[Bug 1244736] Re: upstart configuration for user launches an extra ssh-agent

[Guillaume Martres]

Using:
grep -q "^use-ssh-agent$" /etc/X11/Xsession.options || { stop; exit 0; }
To detect whether or not to launch the ssh agent doesn't seem to make sense to me, since if "use-ssh-agent" is true then ssh-agent will be setup by /etc/X11/Xsession.d/90x11-common_ssh-agent (and later launched), so there doesn't seem to be a need for an upstart script here.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1244736

Title:
  upstart configuration for user launches an extra ssh-agent

Status in “gnome-session” package in Ubuntu:
  Confirmed
Status in “openssh” package in Ubuntu:
  Confirmed

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/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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1244736/+subscriptions