Forward gpg-agent to container

Werner Koch wk at gnupg.org
Tue Jun 5 16:50:54 CEST 2018


On Tue,  5 Jun 2018 08:56, andrewg at andrewg.com said:

> This sounds overly complicated. Once you have the extra socket visible
> inside the container, it should be sufficient to set the environment
> variable GPG_AGENT_SOCK. You don’t need to start an extra agent inside

The envvar GPG_AGENT_INFO is not more supported since 2.1.

I don't know how to best convey and share the socket using the file
system.  I have always used ssh features for this.  Actually I am also
using ssh to connect to other accounts on my box (autmates xauth
handling :-).


Salam-Shalom,

   Werner

-- 
#  Please read:  Daniel Ellsberg - The Doomsday Machine  #
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180605/fe54c668/attachment-0001.sig>


More information about the Gnupg-users mailing list