regression handling keyserver directives [was: Re: [Announce] GnuPG 2.2.20 released]

[Daniel Kahn Gillmor]

On Sun 2020-03-22 19:10:46 -0400, Phil Pennock via Gnupg-devel wrote:
> On 2020-03-20 at 17:51 +0100, Werner Koch via Gnupg-devel wrote:
>> We are pleased to announce the availability of a new GnuPG release:
>> version 2.2.20.
>
> There appears to be a regression in handling keyserver directives, in
> ~/.gnupg/gpg.conf or on the command-line.
>
>     % gpg --recv-key $my_key
>     gpg: keyserver receive failed: Invalid URI

I've just built and tested and uploaded 2.2.20 for debian, and i'm not
seeing this particular failure here.

> As near as I can determine, anything hkps: triggers this, as does
> `keys.openpgp.org`, but if I can find another functioning non-HKPS HKP
> keyserver, then I can use that.
>
> For `keys.openpgp.org`, `hkp://`, `hkps://`, or bare hostname, all
> trigger this.
>
> I haven't yet found a common trigger to isolate this, unless it's
> existence of MX records in DNS, which seems unlikely.

Have you stopped any older already-running instances of dirmngr?

I'd be happy to help debug further, but maybe it would help to post some
logs from dirmngr or something to see what might be going wrong.

     --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20200323/83ffc417/attachment-0001.sig>