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

[Phil Pennock]

On 2020-03-23 at 15:29 -0400, Daniel Kahn Gillmor wrote:
> I've just built and tested and uploaded 2.2.20 for debian, and i'm not
> seeing this particular failure here.

Drat.

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

Not only that, I'd even rebooted since.

> 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.

Sure.  I considered holding off for debugging but I didn't have time
then, so figured it was worth saying something in case it was an easy
fix.  Also: sorry for not changing the mail subject.

The packages are my own builds, these are the version numbers:

    gmp          6.2.0
    gnupg        2.2.20
    gnutls       3.6.12
    libassuan    2.5.3
    libgcrypt    1.8.5
    libgpg-error 1.37
    libksba      1.3.5
    nettle       3.5.1
    npth         1.6
    pinentry     1.1.0

With verbose / debug-all / gnutls-debug 9 :

~~~~~~~~~~~~~~~~~~~~~~~~~~~8< log.dirmngr >8~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2020-03-23 18:11:38 dirmngr[20128.0] permanently loaded certificates: 66
2020-03-23 18:11:38 dirmngr[20128.0]     runtime cached certificates: 0
2020-03-23 18:11:38 dirmngr[20128.0]            trusted certificates: 66 (65,0,0,1)
2020-03-23 18:11:38 dirmngr[20128.6] handler for fd 6 started
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> # Home: /home/pdp/.gnupg
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> # Config: /home/pdp/.gnupg/dirmngr.conf
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> OK Dirmngr 2.2.20 at your service
2020-03-23 18:11:38 dirmngr[20128.6] connection from process 20127 (1000:1000)
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 <- GETINFO version
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> D 2.2.20
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> OK
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 <- KEYSERVER --clear hkps://keys.openpgp.org
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> OK
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 <- KEYSERVER
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> S KEYSERVER hkps://keys.openpgp.org
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> OK
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 <- KS_GET -- 0x4833892924C60A7AE666D32A1DA3E68F41CEECAC
2020-03-23 18:11:38 dirmngr[20128.6] DBG: dns: libdns initialized
2020-03-23 18:11:38 dirmngr[20128.6] DBG: dns: getsrv(_pgpkey-https._tcp.keys.openpgp.org) -> 0 records
2020-03-23 18:11:38 dirmngr[20128.6] DBG: dns: resolve_dns_name(keys.openpgp.org): Success
2020-03-23 18:11:38 dirmngr[20128.6] resolve_dns_addr for 'keys.openpgp.org': 'keys.openpgp.org' [already known]
2020-03-23 18:11:38 dirmngr[20128.6] resolve_dns_addr for 'keys.openpgp.org': 'keys.openpgp.org' [already known]
2020-03-23 18:11:38 dirmngr[20128.6] command 'KS_GET' failed: Invalid URI
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> ERR 167772207 Invalid URI <Dirmngr>
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 <- BYE
2020-03-23 18:11:38 dirmngr[20128.6] DBG: chan_6 -> OK closing connection
2020-03-23 18:11:38 dirmngr[20128.6] handler for fd 6 terminated
~~~~~~~~~~~~~~~~~~~~~~~~~~~8< log.dirmngr >8~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-Phil