> On 5. Jun 2018, at 08:56, Andrew Gallagher <andr...@andrewg.com> wrote: > >> >> On 4 Jun 2018, at 19:44, Benjamin Kircher <benjamin.kirc...@gmail.com> 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 extra-socket. Here is what I am doing: > > 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 container.
Andrew, thanks for looking into this. Is this documented somewhere? I can’t find this environment variable in the man-pages and a quick code search over gnupg, libassuan, gpgme, and friends shows no such environment variable. BK _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
