From ssh point of view gnome-keyring is trying to behave as a ssh-agent. So
https://bugzilla.novell.com/show_bug.cgi?id=436352 User mhrusecky@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=436352#c10 Michal Hrusecky <mhrusecky@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |anicka@novell.com Component|Basesystem |GNOME Info Provider|sbrabec@novell.com | AssignedTo|anicka@novell.com |bnc-team-gnome@forge.provo. | |novell.com --- Comment #10 from Michal Hrusecky <mhrusecky@novell.com> 2009-02-10 09:30:15 MST --- there is probably no clean way how to select appropriate keyring - this should be done on gnome-keyring side. Problem with default pop-up that appears is that it is trying to create new keyring and it doesn't state any reason why. It would be nice to let user know that it is requesting new keyring for ssh and let the user choose if he wants to use his default keyring. Unlocking ssh key is better as it states what key are we trying to open but it prevents user from doing anything else till he enter his password or cancel unlocking. This can be quite confusing and obstructing too. For example it is again non-obvious who is trying to unlock this key. And if I'm connecting to some distant server over some slow connection, it may take some time before pop-up appears, it may catch me in the middle of some other work and it will steal my keyboard even if I focus some other window to try to find out what's going on... I think these problems needs to be solved and I guess it will be better to disable ssh integration of gnome-keyring until these things will be solved. But it seems like this is mainly gnome-keyring integration problem and therefor it should be decided by gnome-keyring maintainers. -- 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.