after a very short and helpful conversation with the gnome-keyring
developers this problem is now resolved.
The problem is that the way gnome-keyring checks for public/private keys
has changed.
The old process used to check for ~/.ssh/id_?sa
now it checks for a matching public key in a *.pub format too.
For gnome-keyring to actually prompt you to unlock the key, both the
public and private keys must be in your local ~/.ssh directory, this is
why some users are seeing this as a problem, and others not.
I was always keen to keep my public and private keys separate for legacy
security issues, I've just dumped my public key with a .pub extension in
my ~/.ssh directory and gnome-keyring started working, bang. No
technical problem, just user error and a lack of information about the
changes to gnome-keyring package in the ubuntu community/packager.
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => Fix Released
--
ssh-askpass-gnome doesn't prompt for password in any release post ubuntu 8.10
32/64bit
https://bugs.launchpad.net/bugs/578035
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
