From gnupg-users Thu Apr 19 13:21:32 2018 From: Laszlo Papp Date: Thu, 19 Apr 2018 13:21:32 +0000 To: gnupg-users Subject: Re: dirmngr timeout Message-Id: X-MARC-Message: https://marc.info/?l=gnupg-users&m=152414412312898 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============4294838950303932228==" --===============4294838950303932228== Content-Type: multipart/alternative; boundary="0000000000004574df056a337316" --0000000000004574df056a337316 Content-Type: text/plain; charset="UTF-8" OK, so I have now solved this issue by running the following commands in docker prior to running gpg: install -dm700 ~/.gnupg; echo honor-http-proxy > ~/.gnupg/dirmngr.conf On Thu, Apr 19, 2018 at 11:04 AM, Laszlo Papp wrote: > Adding the list back. > > On Thu, Apr 19, 2018 at 9:31 AM, Laszlo Papp wrote: > >> >> >> On Wed, Apr 18, 2018 at 9:02 PM, Daniel Kahn Gillmor < >> dkg@fifthhorseman.net> wrote: >> >>> Hi Laszlo-- >>> >>> I'm afraid we don't know the details of how your docker instance is set >>> up; which versions of which packages you have installed inside docker >>> vs. outside of docker, what's bind-mounted, what the networking >>> constraints are in place. this makes debugging remotely a bit more >>> difficult. >>> >> >> OK; I am happy to share this. Thank you for following up with your >> difficulties. >> >> It is bleeding edge Archlinux both inside and outside. gpg and dirmngr >> are at the latest release, 2.2.6. >> >> Nothing is bind-mounted. >> >> There are no networking constraints in place as far as I am aware. >> >> Hope this makes debugging remotely a bit easier. >> >> >>> On Fri 2018-04-13 15:29:50 +0100, Laszlo Papp wrote: >>> > gpg: connecting dirmngr at '/home/nic/.gnupg/S.dirmngr' failed: IPC >>> connect call failed >>> > gpg: keyserver receive failed: No dirmngr >>> >>> if a standard user runtime dir is mounted on /run/user/$UID , the >>> dirmngr socket could be mounted there. It sounds like that is probably >>> not mounted, so gpg is falling back to the socket location in the home >>> directory. >>> >> >> That is right. >> >> >>> but if no dirmngr is running listening on the expected socket, then gpg >>> normally tries to launch it itself. >>> >> >> Correct. >> >> >>> for example, i'd expect to see the following: >>> >>> gpg-connect-agent: no running Dirmngr - starting '/usr/bin/dirmngr' >>> gpg-connect-agent: waiting for the dirmngr to come up ... (5s) >>> gpg-connect-agent: waiting for the dirmngr to come up ... (4s) >>> gpg-connect-agent: connection to dirmngr established >>> >> >>> But i don't see that in your logs. What version of GnuPG is installed? >>> >> >> 2.2.6 >> >> >>> how did dirmnger get installed on this docker system? how did gpg >>> itself get installed? >>> >> >> pacman (Archlinux package manager). >> >> >>> >>> what is the output of: >>> >>> gpgconf --list-dirs >>> >>> (within the docker instance, that is) >>> >> >> sysconfdir:/etc/gnupg >> bindir:/usr/bin >> libexecdir:/usr/lib/gnupg >> libdir:/usr/lib/gnupg >> datadir:/usr/share/gnupg >> localedir:/usr/share/locale >> socketdir:/home/nic/.gnupg >> dirmngr-socket:/home/nic/.gnupg/S.dirmngr >> agent-ssh-socket:/home/nic/.gnupg/S.gpg-agent.ssh >> agent-extra-socket:/home/nic/.gnupg/S.gpg-agent.extra >> agent-browser-socket:/home/nic/.gnupg/S.gpg-agent.browser >> agent-socket:/home/nic/.gnupg/S.gpg-agent >> homedir:/home/nic/.gnupg >> >> Yes, I meant "systemctl --user import-environment http_proxy". That was a >> typo; sorry about that. >> >> I am looking forward to resolving this. Hopefully, the information above >> helps. What should I try next? >> >> Best regards, L. >> > > --0000000000004574df056a337316 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
OK, so I have now solved this issue by running the followi= ng commands in docker prior to running gpg:

install -dm7= 00 ~/.gnupg; echo honor-http-proxy > ~/.gnupg/dirmngr.conf

On Thu, Apr 19,= 2018 at 11:04 AM, Laszlo Papp <lpapp@kde.org> wrote:
Adding the list back.

On Thu, Apr 19, 2018 at 9:31 AM, Laszlo Papp <lpapp@kde.org> wrote:

On Wed, Ap= r 18, 2018 at 9:02 PM, Daniel Kahn Gillmor <dkg@fifthhorseman.net&= gt; wrote:
Hi L= aszlo--

I'm afraid we don't know the details of how your docker instance is= set
up; which versions of which packages you have installed inside docker
vs. outside of docker, what's bind-mounted, what the networking
constraints are in place.=C2=A0 this makes debugging remotely a bit more difficult.

OK; I am happy to sha= re this. Thank you for following up with your difficulties.

<= /div>
It is bleeding edge Archlinux both inside and outside. gpg and di= rmngr are at the latest release, 2.2.6.

Nothing is= bind-mounted.

There are no networking constraints= in place as far as I am aware.

Hope this makes de= bugging remotely a bit easier.
=C2=A0
On Fri 2018-04-13 15:29:50 +0100, Laszlo Papp wrote= :
> gpg: connecting dirmngr at '/home/nic/.gnupg/S.dirmngr' failed= : IPC connect call failed
> gpg: keyserver receive failed: No dirmngr

if a standard user runtime dir is mounted on /run/user/$UID , the dirmngr socket could be mounted there.=C2=A0 It sounds like that is probabl= y
not mounted, so gpg is falling back to the socket location in the home
directory.

That is right.
<= span>
=C2=A0
but= if no dirmngr is running listening on the expected socket, then gpg
normally tries to launch it itself.

<= div>Correct.
=C2=A0
for example, i'd expect to see the following:

=C2=A0 =C2=A0 gpg-connect-agent: no running Dirmngr - starting '/usr/bi= n/dirmngr'
=C2=A0 =C2=A0 gpg-connect-agent: waiting for the dirmngr to come up ... (5s= )
=C2=A0 =C2=A0 gpg-connect-agent: waiting for the dirmngr to come up ... (4s= )
=C2=A0 =C2=A0 gpg-connect-agent: connection to dirmngr established

But i don't see that in your logs.=C2=A0 What version of GnuPG is insta= lled?

2.2.6
=C2= =A0
how did dirmnger= get installed on this docker system?=C2=A0 how did gpg
itself get installed?

pacman (Ar= chlinux package manager).
=C2=A0

what is the output of:

=C2=A0 =C2=A0 =C2=A0gpgconf --list-dirs

(within the docker instance, that is)

sysconfdir:/etc/gnupg
bindir:/usr/bin
libexe= cdir:/usr/lib/gnupg
libdir:/usr/lib/gnupg
datadir:/usr/= share/gnupg
localedir:/usr/share/locale
socketdir:/home= /nic/.gnupg
dirmngr-socket:/home/nic/.gnupg/S.dirmngr
<= div>agent-ssh-socket:/home/nic/.gnupg/S.gpg-agent.ssh
agent-= extra-socket:/home/nic/.gnupg/S.gpg-agent.extra
agent-browse= r-socket:/home/nic/.gnupg/S.gpg-agent.browser
agent-socket:/= home/nic/.gnupg/S.gpg-agent
homedir:/home/nic/.gnupg

Yes, I meant "systemctl --user import-environm= ent http_proxy". That was a typo; sorry about that.
<= div class=3D"gmail_extra">
I am looking forward to resolving this. Hopef= ully, the information above helps. What should I try next?

Best regards, L.


--0000000000004574df056a337316-- --===============4294838950303932228== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users --===============4294838950303932228==--