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

[Alex Mauer]

I really like this, but I think it could be improved:
You don’t really need to pass --enable-ssh-support.

Instead, you can place the option in the gpg-agent.conf file (~/.gnupg
/gpg-agent.conf)

This way there is no need to worry about competing with ssh-agent.

So the only thing to really worry about then, is exporting the
appropriate environment variables, and it should be palatable to ssh-
agent users.

I think this change could be included in the official package too, with
no problem.

There is some inconsistency among the various *-agents though: To
disable the ssh-agent you edit /etc/X11/Xsession.options; to enable the
gpg-agent you edit ~/.gnupg/gpg.conf; to enable ssh support in gpg you
edit ~/.gnupg/gpg-agent.conf; and to disable ssh support in gnome-
keyring (the default) you have to hack around in /etc/xdg/autostart
/gnome-keyring-*.desktop. It’s a real mess.

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