Asks to unlock private key that was already unlocked by ssh-add(1)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-keyring (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
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:
$ ssh-add ~/.ssh/id_rsa_foo /srv/local/
Enter passphrase for /home/skunk/
Identity added: /home/skunk/
Identity added: /srv/local/
Identity added: /srv/local/
$ ssh-add -l
2048 97:ea:51:
2048 f9:3b:29:
2048 ac:c2:c3:
2048 97:ea:51:
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.