Public bug reported:
Symptom: the ssh-agent does not have my key anymore after upgrade to
13.10
I use kdm and pam-ssh to deal with my keys.
It appears that pam-ssh does its job, and my key it actually there... in
another agent: I can see 2 ssh-agent processes, and changing the
SSH_AUTH_SOCK and SSH_AGENT_PID environment variables so that they refer
to the other one reveals my key...
The script /usr/share/upstart/sessions/ssh-agent.conf launches ssh-
agent, regardless of whether it is already there or not.
Adding the line:
[ "$SSH_AGENT_PID" ] && { stop; exit 0; } # already running
before line:
eval "$(ssh-agent)" >/dev/null
in the script does restore the behavior before upgrade.
** Affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1244736
Title:
upstart configuration for user launches an extra ssh-agent
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1244736/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
