Asks to unlock private key that was already unlocked by ssh-add(1)

[Daniel Richard G.]

This concerns gnome-keyring 3.6.1-0ubuntu1 in Ubuntu Quantal.

Normally, I invoke ssh-add(1) manually after logging in. I add a number of identities, and then connect to other hosts using those identities. This worked correctly in Ubuntu Oneiric.

Now, with a new Quantal install, when I connect to another host I am confronted with a dialog to unlock the same private key that should have been unlocked with ssh-add. If I type in my passphrase again into this dialog, the connection succeeds and the identity is cached, but of course the agent should not be requesting the passphrase a second time.

I suspect the problem is that the agent is counting one of my private keys twice:

$ ssh-add -l
2048 97:ea:51:11:53:94:14:7f:25:f2:b0:f5:a8:54:04:56 foo@bar (RSA)

$ ssh-add ~/.ssh/id_rsa_foo /srv/local/ssh/id_rsa_{blah,xyzzy}
Enter passphrase for /home/skunk/.ssh/id_rsa_foo:
Identity added: /home/skunk/.ssh/id_rsa_foo (/home/skunk/.ssh/id_rsa_foo)
Identity added: /srv/local/ssh/id_rsa_blah (/srv/local/ssh/id_rsa_blah)
Identity added: /srv/local/ssh/id_rsa_xyzzy (/srv/local/ssh/id_rsa_xyzzy)

$ ssh-add -l
2048 97:ea:51:11:53:94:14:7f:25:f2:b0:f5:a8:54:04:56 /home/skunk/.ssh/id_rsa_foo (RSA)
2048 f9:3b:29:60:b3:59:69:e2:c3:d8:09:cd:d2:8b:a0:08 /srv/local/ssh/id_rsa_blah (RSA)
2048 ac:c2:c3:ac:b9:ae:e5:c9:85:85:71:18:3c:0f:2a:a1 /srv/local/ssh/id_rsa_xyzzy (RSA)
2048 97:ea:51:11:53:94:14:7f:25:f2:b0:f5:a8:54:04:56 foo@bar (RSA)

Notice how the "97:ea:51:11:..." key is listed twice in the second "ssh-add -l" listing. When the unlock-private-key dialog comes up, it is for the "foo@bar" identity, and gnome-keyring's failure to recognize that id_rsa_foo is the selfsame key is probably the crux of this bug.