Re: Forward gpg-agent to container

2018-06-05 Thread Phil Pennock
On 2018-06-05 at 17:17 -0400, Phil Pennock wrote: > Shell 2: > $ docker run -it --rm -v /var/run/pdp.gnupg:/root/.gnupg/S.gpg-agent.ssh > alpine > / # chmod 0700 /root/.gnupg && chown root:root /root/.gnupg/S.gpg-agent > / # apk update && apk add --no-cache gnupg I apologise, I missed fixing one

Re: Forward gpg-agent to container

2018-06-05 Thread Phil Pennock
On 2018-06-05 at 20:18 +0200, Peter Lebbing wrote: > Have you tried by hand whether the concept of communicating over a > socket to a container works at all? You could use socat to create a > socket and communicate, one socat on your host system and one inside the > container. > > I have no

Re: Forward gpg-agent to container

2018-06-05 Thread Aleksandar Lazic
Hi. On 05/06/2018 18:02, Benjamin Kircher wrote: On 5. Jun 2018, at 10:54, Benjamin Kircher wrote: On 5. Jun 2018, at 08:56, Andrew Gallagher wrote: On 4 Jun 2018, at 19:44, Benjamin Kircher wrote: Now inside the container I can see my socket # ls -l /gpg-agent srwx-- 1 root

Re: Forward gpg-agent to container

2018-06-05 Thread Peter Lebbing
On 04/06/18 20:44, Benjamin Kircher wrote: > For this I create a bind mount of agent-extra-socket to /gpg-agent inside the > container Have you tried by hand whether the concept of communicating over a socket to a container works at all? You could use socat to create a socket and communicate,

Re: Forward gpg-agent to container

2018-06-05 Thread Benjamin Kircher
Hello Werner, > On 5. Jun 2018, at 16:50, Werner Koch wrote: > > The envvar GPG_AGENT_INFO is not more supported since 2.1. I saw that, too. Andrew was mentioning GPG_AGENT_SOCK, not GPG_AGENT_INFO however. > I don't know how to best convey and share the socket using the file > system. I

Re: Forward gpg-agent to container

2018-06-05 Thread Benjamin Kircher
> On 5. Jun 2018, at 10:54, Benjamin Kircher wrote: > > > >> On 5. Jun 2018, at 08:56, Andrew Gallagher wrote: >> >>> >>> On 4 Jun 2018, at 19:44, Benjamin Kircher >>> wrote: >>> >>> Now inside the container I can see my socket >>> >>> # ls -l /gpg-agent >>> srwx-- 1 root root 0

Re: Forward gpg-agent to container

2018-06-05 Thread Werner Koch
On Tue, 5 Jun 2018 08:56, andr...@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

Re: Forward gpg-agent to container

2018-06-05 Thread Benjamin Kircher
> On 5. Jun 2018, at 08:56, Andrew Gallagher wrote: > >> >> On 4 Jun 2018, at 19:44, Benjamin Kircher wrote: >> >> Now inside the container I can see my socket >> >> # ls -l /gpg-agent >> srwx-- 1 root root 0 Jun 4 17:45 /gpg-agent >> >> From here on, I am kind of stuck. I fail to

Re: Forward gpg-agent to container

2018-06-05 Thread Andrew Gallagher
> On 4 Jun 2018, at 19:44, Benjamin Kircher wrote: > > Now inside the container I can see my socket > > # ls -l /gpg-agent > srwx-- 1 root root 0 Jun 4 17:45 /gpg-agent > > From here on, I am kind of stuck. I fail to somehow make gpg-agent inside the > container “use” the