On 08.08.2022 16:13, Corinna Vinschen wrote:
On Aug 8 21:13, Yasuhiro Kimura wrote:
From: Corinna Vinschen
IIUC, that should be fixable by configuring gnupg with --disable-libdns.
Corinna
Thanks Corinna,
I will upload shortly a version "2.2.35-2" implementing this configuration
Regards
Corinna Vinschen wrote:
IIUC, that should be fixable by configuring gnupg with --disable-libdns.
Yes, below is the message that I sent to Marco but which was rejected by
this list because I wasn't subscribed at the time that I replied to all.
--
-Chad
On 2022-08-07 10:34, Marco
On Aug 8 21:13, Yasuhiro Kimura wrote:
> From: Corinna Vinschen
> Subject: Re: resolv.conf and gnupg2
> Date: Mon, 8 Aug 2022 09:30:47 +0200
>
> > I can't believe (but may be wrong, of course) that gnupg2 tries to
> > access /etc/resolv.conf by itself. I would
From: Corinna Vinschen
Subject: Re: resolv.conf and gnupg2
Date: Mon, 8 Aug 2022 09:30:47 +0200
> I can't believe (but may be wrong, of course) that gnupg2 tries to
> access /etc/resolv.conf by itself. I would rather guess that gnupg2
> is linked against one or more libs provided by
On Aug 8 09:30, Corinna Vinschen wrote:
> On Aug 7 16:34, Marco Atzeri wrote:
> > Hi,
> >
> > currently as default Gnupg 2.x is unable to contact keyservers and recover
> > any key. Gnupg 1.x has not such problem
> >
> > $ /usr/bin/gpg2 --keyserver pgp.mit.edu --recv-keys 5981E818 gpg:
On Aug 8 11:15, ASSI wrote:
> Mark Geisert writes:
> > Could Cygwin itself provide a minimal /etc/resolv.conf pointing to
> > public DNS server(s)? Some users might object to Google's public DNS
> > (e.g. 8.8.8.8) though.
>
> No, this would be the job for any software that configures the DNS
>
Mark Geisert writes:
> Could Cygwin itself provide a minimal /etc/resolv.conf pointing to
> public DNS server(s)? Some users might object to Google's public DNS
> (e.g. 8.8.8.8) though.
No, this would be the job for any software that configures the DNS
resolver. However, I'd prefer if no
On Aug 7 16:34, Marco Atzeri wrote:
> Hi,
>
> currently as default Gnupg 2.x is unable to contact keyservers and recover
> any key. Gnupg 1.x has not such problem
>
> $ /usr/bin/gpg2 --keyserver pgp.mit.edu --recv-keys 5981E818 gpg: keyserver
> receive failed: No such file or directory
>
>
Marco Atzeri wrote:
Hi,
currently as default Gnupg 2.x is unable to contact keyservers and recover any
key. Gnupg 1.x has not such problem
$ /usr/bin/gpg2 --keyserver pgp.mit.edu --recv-keys 5981E818 gpg: keyserver
receive failed: No such file or directory
The cryptic message is due to