[prev in list] [next in list] [prev in thread] [next in thread]
List: gnupg-users
Subject: Re: dirmngr timeout
From: Laszlo Papp <lpapp () kde ! org>
Date: 2018-04-19 13:21:32
Message-ID: CAOMwXhNbUy3qhC-xg8dQfmJZ5BZ0Ek6SmCMp7rPYyr=c8D1cDg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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@kde.org> wrote:
> Adding the list back.
>
> On Thu, Apr 19, 2018 at 9:31 AM, Laszlo Papp <lpapp@kde.org> 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.
>>
>
>
[Attachment #5 (text/html)]
<div dir="ltr">OK, so I have now solved this issue by running the following commands \
in docker prior to running gpg:<div><br></div><div>install -dm700 ~/.gnupg; echo \
honor-http-proxy > ~/.gnupg/dirmngr.conf<br></div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 19, 2018 at 11:04 AM, \
Laszlo Papp <span dir="ltr"><<a href="mailto:lpapp@kde.org" \
target="_blank">lpapp@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Adding the list back.</div><div \
class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div \
class="gmail_quote">On Thu, Apr 19, 2018 at 9:31 AM, Laszlo Papp <span \
dir="ltr"><<a href="mailto:lpapp@kde.org" \
target="_blank">lpapp@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div \
class="gmail_quote"><span>On Wed, Apr 18, 2018 at 9:02 PM, Daniel Kahn Gillmor <span \
dir="ltr"><<a href="mailto:dkg@fifthhorseman.net" \
target="_blank">dkg@fifthhorseman.net</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi Laszlo--<br> <br>
I'm afraid we don't know the details of how your docker instance is set<br>
up; which versions of which packages you have installed inside docker<br>
vs. outside of docker, what's bind-mounted, what the networking<br>
constraints are in place. this makes debugging remotely a bit more<br>
difficult.<br></blockquote><div><br></div></span><div>OK; I am happy to share this. \
Thank you for following up with your difficulties.</div><div><br></div><div>It is \
bleeding edge Archlinux both inside and outside. gpg and dirmngr are at the latest \
release, 2.2.6.</div><div><br></div><div>Nothing is \
bind-mounted.</div><div><br></div><div>There are no networking constraints in place \
as far as I am aware.</div><div><br></div><div>Hope this makes debugging remotely a \
bit easier.</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px \
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span \
class="m_1123813940257374899m_1663019961457233920gmail-">On Fri 2018-04-13 15:29:50 \
+0100, Laszlo Papp wrote:<br> > gpg: connecting dirmngr at \
'/home/nic/.gnupg/S.dirmngr' failed: IPC connect call failed<br> > gpg: \
keyserver receive failed: No dirmngr<br> <br>
</span>if a standard user runtime dir is mounted on /run/user/$UID , the<br>
dirmngr socket could be mounted there. It sounds like that is probably<br>
not mounted, so gpg is falling back to the socket location in the home<br>
directory.<br></blockquote><div><br></div></span><div>That is right.</div><span><div> \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex">but if no dirmngr is running listening on \
the expected socket, then gpg<br> normally tries to launch it \
itself.<br></blockquote><div><br></div></span><div>Correct.</div><span><div> \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex">for example, i'd expect to see the \
following:<br> <br>
gpg-connect-agent: no running Dirmngr - starting '/usr/bin/dirmngr'<br>
gpg-connect-agent: waiting for the dirmngr to come up ... (5s)<br>
gpg-connect-agent: waiting for the dirmngr to come up ... (4s)<br>
gpg-connect-agent: connection to dirmngr \
established<br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br> But i don't \
see that in your logs. What version of GnuPG is \
installed?<br></blockquote><div><br></div></span><div>2.2.6</div><span><div> \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex">how did dirmnger get installed on this \
docker system? how did gpg<br> itself get \
installed?<br></blockquote><div><br></div></span><div>pacman (Archlinux package \
manager).</div><span><div> </div><blockquote class="gmail_quote" style="margin:0px \
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
what is the output of:<br>
<br>
gpgconf --list-dirs<br>
<br>
(within the docker instance, that \
is)<br></blockquote><div><br></div></span><div><div>sysconfdir:/etc/gnupg</div><div>bi \
ndir:/usr/bin</div><div>libexecdir:/usr/lib/gnupg</div><div>libdir:/usr/lib/gnupg</div \
><div>datadir:/usr/share/gnupg</div><div>localedir:/usr/share/locale</div><div>socketd \
> ir:/home/nic/.gnupg</div><div>dirmngr-socket:/home/nic/.gnup<wbr>g/S.dirmngr</div><d \
> iv>agent-ssh-socket:/home/nic/.gn<wbr>upg/S.gpg-agent.ssh</div><div>agent-extra-sock \
> et:/home/nic/.<wbr>gnupg/S.gpg-agent.extra</div><div>agent-browser-socket:/home/nic< \
> wbr>/.gnupg/S.gpg-agent.browser</div><div>agent-socket:/home/nic/.gnupg/<wbr>S.gpg-agent</div><div>homedir:/home/nic/.gnupg</div></div><div><br></div><div>Yes, \
> I meant "systemctl --user import-environment http_proxy". That was a \
> typo; sorry about that.</div></div></div><div class="gmail_extra"><br>I am looking \
> forward to resolving this. Hopefully, the information above helps. What should I \
> try next?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Best \
> regards, L.</div></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic