upstart configuration for user launches an extra ssh-agent
Bug #1244736 reported by
Bruno Vasselle
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-session (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
openssh (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
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/
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.
Changed in openssh (Ubuntu): | |
status: | New → Confirmed |
To post a comment you must log in.
This does not affect "gnome-session", but "openssh-client"... I'm pretty sure I've said so before posting.