Re: dirmngr timeout

2018-04-19 Thread 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 wrote: > Adding the list back. > > On Thu, Apr 19, 2018 at 9:3

Re: dirmngr timeout

2018-04-19 Thread Laszlo Papp
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 < > d...@fifthhorseman.net> wrote: > >> Hi Laszlo-- >> >> I'm afraid we don't know the details of how your dock

Re: dirmngr timeout

2018-04-18 Thread Laszlo Papp
I still have not managed to solve this. Does anyone have an idea? On Fri, Apr 13, 2018 at 3:29 PM, Laszlo Papp wrote: > Unfortunately, I am seeing the following issue in docker, still. What > would be the solution to this? I am using 2.2.6. > > Step 12/46 : RUN dirmngr < /d

Re: dirmngr timeout

2018-04-13 Thread Laszlo Papp
Unfortunately, I am seeing the following issue in docker, still. What would be the solution to this? I am using 2.2.6. Step 12/46 : RUN dirmngr < /dev/null && echo "honor_http_proxy" > /home/nic/.gnupg/dirmngr.conf && touch ~/.gnupg/dirmngr_ldapservers.conf && ls -ld ~/.gnupg && gpg --keyserver h

Re: dirmngr timeout

2018-04-13 Thread Laszlo Papp
On Fri, Apr 13, 2018 at 10:46 AM, Werner Koch wrote: > On Thu, 12 Apr 2018 15:45, lp...@kde.org said: > > [Full quote trimmed] > > It looks like if I run dirmngr manually, as follows, with > honor-http-proxy, > > gpg works: > > > > dirmngr --daemon > > It will also work if dirnmnr is automaticall

Re: dirmngr timeout

2018-04-12 Thread Laszlo Papp
On Thu, Apr 12, 2018 at 9:30 AM, Laszlo Papp wrote: > > > On Wed, Apr 11, 2018 at 8:09 PM, Werner Koch wrote: > >> On Tue, 10 Apr 2018 17:19, lp...@kde.org said: >> >> > Proxy request sent, awaiting response... 200 OK >> > Length: 58162 (57K) [applica

Re: dirmngr timeout

2018-04-12 Thread Laszlo Papp
On Wed, Apr 11, 2018 at 8:09 PM, Werner Koch wrote: > On Tue, 10 Apr 2018 17:19, lp...@kde.org said: > > > Proxy request sent, awaiting response... 200 OK > > Length: 58162 (57K) [application/pgp-keys] > > Okay that works. Now we need to see why dirmngr has a different idea. > When we first talk

Re: dirmngr timeout

2018-04-10 Thread Laszlo Papp
On Tue, Apr 10, 2018 at 3:29 PM, Werner Koch wrote: > On Tue, 10 Apr 2018 14:29, lp...@kde.org said: > > > wget -4 -v -O/dev/null http://80.108.201.53:80 > > Please try this also: > > wget -vOx 'http://80.108.201.53:80/pks/lookup?op=get&options=mr&; > search=0x702353E0F7E48EDB' > > This is the a

dirmngr timeout

2018-04-10 Thread Laszlo Papp
>] 4.89K --.-KB/sin 0.001s 2018-04-10 13:00:49 (4.98 MB/s) - ‘/dev/null’ saved [5004/5004] Yes, I do have a corporate proxy, however, the environment variables are set up properly. Other applications work. Having said that, port 80 is used h

dirmngr timeout

2018-04-10 Thread Laszlo Papp
===>] 4.89K --.-KB/sin 0.001s 2018-04-10 13:00:49 (4.98 MB/s) - ‘/dev/null’ saved [5004/5004] Yes, I do have a corporate proxy, however, the environment variables are set up properly. Other applications work. Having said that, port 80 is