dirmngr timeout

[Laszlo Papp]

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 <lpapp at kde.org> wrote:

> Adding the list back.
>
> On Thu, Apr 19, 2018 at 9:31 AM, Laszlo Papp <lpapp at kde.org> wrote:
>
>>
>>
>> On Wed, Apr 18, 2018 at 9:02 PM, Daniel Kahn Gillmor <
>> dkg at 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.
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180419/d2779826/attachment.html>