On Tue, Mar 03, 2009 at 09:18:46AM -0600, Robert Nichols wrote: > Cameron Simpson wrote: >> Go: >> >> env | grep '^SSH' >> >> Is there an SSH_AUTH_SOCK? >> >> Find the ssh and kill it. Or modify your envionment sufficiently to gain >> control over the ssh-agent (or simply start your own). By using the -t >> option to ssh-agent when you start it you can control how long an added >> key starts "good". You can also add a key with ssh-add and specify a >> timeout then. > > The process at the other end of $SSH_AUTH_SOCK is > "gnome-keyring-daemon -d -login". That process gets created when I log > in. Killing it doesn't strike me as a good idea. Indeed, other keyring > related stuff breaks if I do that. Does this page help you at all? http://live.gnome.org/GnomeKeyring/Ssh -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
Attachment:
pgpsU5FavTdxZ.pgp
Description: PGP signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
