Comment 19 for bug 328127

Revision history for this message
CPKS (c-1) wrote :

I upgraded to Jaunty last night, and now I have this problem (2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux).

Unlike the previous commenter, I was getting no request for my password to unlock the keyring.

Having read through the comments on bug #328445, I found that a temporary workaround - which will work for all processes, is to ascertain the value of SSH_AUTH_SOCK. On my system it has the following value:

$ echo $SSH_AUTH_SOCK
/tmp/keyring-nWDqUT/socket.ssh

This file doesn't exist. However, there is another directory in /tmp called ssh-gPkVBp3144 and this contains just the file agent.3144. If I execute

$ ln /tmp/ssh-gPkVBp3144/agent.3144 /tmp/keyring-nWDqUT/socket.ssh

Then SSH authenticates fine.