I believe I am seeing the same bug. Attempts to add my ssh key to the
ssh-agent fail with "Could not open a connection to your authentication
agent."
Here is my /etc/pam.d/gdm:
#%PAM-1.0
auth requisite pam_nologin.so
auth required pam_env.so readenv=1
auth required pam_env.so readenv=1 envfile=/etc/default/locale
@include pam-ssh-auth
@include common-auth
auth optional pam_gnome_keyring.so
@include common-account
session required pam_limits.so
@include pam-ssh-session
@include common-session
@include pam-ssh-session
session optional pam_gnome_keyring.so auto_start
@include common-password
Running strace with ssh-add produces the following salient output:
socket(PF_FILE, SOCK_STREAM, 0) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
connect(3, {sa_family=AF_FILE, path="/tmp/keyring-7VA4wG/ssh"}, 110) = -1
ECONNREFUSED (Connection refused)
close(3) = 0
write(2, "Could not open a connection to y"..., 58Could not open a connection
to your authentication agent.
) = 58
exit_group(2) = ?
Here's another odd thing. When I run 'env | grep -i ssh' I see:
SSH_AGENT_PID=27069
SSH_AUTH_SOCK=/tmp/keyring-7VA4wG/ssh
But when I 'cat .ssh/agent-myhostname' I see:
SSH_AUTH_SOCK=/tmp/ssh-AtsvA27068/agent.27068; export SSH_AUTH_SOCK;
SSH_AGENT_PID=27069; export SSH_AGENT_PID;
echo Agent pid 27069;
Note that the agent PID is 27069 in both, but they are attempting to use
different ssh_auth_sock's.
Problem didn't show up until a clean install of hardy.
Thanks.
--
libpam-ssh doesn't unlock my key
https://bugs.launchpad.net/bugs/195550
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
