https://bugzilla.novell.com/show_bug.cgi?id=436352 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=436352#c6 Stanislav Brabec <sbrabec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@novell.com Status|NEEDINFO |ASSIGNED Info Provider|sbrabec@novell.com | --- Comment #6 from Stanislav Brabec <sbrabec@novell.com> 2008-10-31 05:57:44 MDT --- gnome-keyring-daemon is an application, which provides a central storage of passwords. The storage itself is protected, typically by password (smart card protection is in development). I guess that there was an intention to store ssh passwords and maybe ssh key passwords in gnome-keyring. To use gnome-keyring, you have to: 1) Application must be started directly or indirectly by gnome-keyring-daemon 2) Required keyring must exist 3) Required keyring must be unlocked 4) You must approve application to access selected password 1) should be done by session management 2) Default keyring should exist by default 3) Unlocking keyring may be done manually (by password pop-up) or automatically (if your keyring uses the same password as your login, keyring may be unlocked automatically during session start by using keyring PAM module). 4) You must approve ssh to access the password, either once (one access to the password is permitted) or permanently (you will be asked never more when selected application tries to access the password) As you see from the description above, gnome-keyring may generate pop-ups when unlocking the keyring and when asking to access the password. But I see one minor issue of GNOME keyring <-> ssh implementation: I am using password-less SSH keys. When logging to another machine, no password is needed at all, but SSH tries to access GNOME keyring anyway (and I get an obsolete pop-up asking for keyring unlocking). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.