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
On Fri 2018-04-13 11:00:59 +0100, Laszlo Papp wrote:
> Yes, I meant to reply yesterday after solving this.
>
> systemd --user import-environment http_proxy
>
> is what I used.
i think you mean:
systemctl --user import-environment http_proxy
Please read the "Environment Commands" section of
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.
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 <
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
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
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 automatically started by gpg or via
gpgconf --launch dirmngr.
> But when it is run
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)
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.
>
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 talked on IRC, someone else reported that he had no
problems with
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=mr;
> search=0x702353E0F7E48EDB'
>
> This
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=mr=0x702353E0F7E48EDB'
This is the actual request dirmngr does. 'x' has the key then; please
check.
> Yes, I do have a
Dear gnupg developers,
I keep getting a timeout for "gpg -v --keyserver hkp://
p80.pool.sks-keyservers.net:80 --recv-key 702353E0F7E48EDB" as follows:
tail -F /home/lpapp/dirmngr.log
2018-04-10 11:58:03 dirmngr[11735.6] DBG: chan_6 -> ERR 167805060
Connection timed out
2018-04-10 11:58:03
Dear gnupg developers,
I keep getting a timeout for "gpg -v --keyserver hkp://
p80.pool.sks-keyservers.net:80 --recv-key 702353E0F7E48EDB" as follows:
tail -F /home/lpapp/dirmngr.log
2018-04-10 11:58:03 dirmngr[11735.6] DBG: chan_6 -> ERR 167805060
Connection timed out
2018-04-10 11:58:03
14 matches
Mail list logo