[Bug 1257706] Re: gpg-agent environment variables not correctly exported

[Dimitri John Ledkov]

gnupg2 is not in main, ubuntu uses gnupg1 by default.
in vivid, and being fixed in sru's for trusty and utopic, upstart is managing user session and launching gnupg-agent (either gnupg1 or gnome-keyring), ditto ssh-agent (either gnupg1 or gnome-keyring).

To integrate this correctly, support should be added to ssh-agent/gnome-
keyring-ssh & gpg-agent/gnome-keyring-gpg to support third alternative,
that is gnupg2's gpg-agent and gnupg2's ssh-agent. Patches against that
are welcome.

With respect to gpg smartcard, on my machine i've copied gnupg-
agent.conf job into ~/.config/upstart/ an tweaked it to export ssh-agent
vairable, and also did "echo manual > ~/.config/upstart/ssh-
agent.override" and thus i'm using gnupg gpg-agent for both ssh & gpg
authentication.

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

Title:
  gpg-agent environment variables not correctly exported

Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  Since Ubuntu 13.10, there is an Upstart script /usr/share/upstart/sessions/gpg-agent.conf which launches the gpg-agent daemon and then export the GPG_AGENT_INFO environment variable:
     initctl set-env --global GPG_AGENT_INFO=$GPG_AGENT_INFO
  This is enough to prevent the /etc/X11/Xsession.d/90gpg-agent script from launching gpg-agent itself, but it's not enough to actually use gpg-agent, you also need to export SSH_AUTH_SOCK and SSH_AGENT_PID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1257706/+subscriptions