[pkg-gnupg-maint] Bug#854359: Bug#854359: gnupg: always fails when --recv-keys

[NIIBE Yutaka]

Hello, Roger,

Roger Shimizu <rogershimizu at gmail.com> wrote:
> While trying to using caff to sign keys, I find I cannot retrieve other
> people's keys. So for debug, I tried to get my own key by:
>
> $ gpg -vvv --debug-all --recv-keys 0x6C6ACD6417B3ACB1

It is the failure of dirmngr which does actual key retrieval.

In my environment, it works fine.  Could you please test dirmngr
directly.  Here is a session example which I did.  My input is "->".

 -> $ mkdir /run/user/1000/test
 -> $ dirmngr --server --homedir=/run/user/1000/test
    dirmngr[2004]: error opening '/run/user/1000/test/dirmngr_ldapservers.conf': No such file or directory
    dirmngr[2004.0]: permanently loaded certificates: 0
    dirmngr[2004.0]:     runtime cached certificates: 0
    # Home: /run/user/1000/test
    # Config: [none]
 -> KS_GET -- 0x6C6ACD6417B3ACB1
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'oteiza.siccegge.de'
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'bone.digitalis.org'
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'prod00.keyserver.dca.witopia.net'
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'gpg.NebrWesleyan.edu'
    dirmngr[2004.0]: resolve_dns_addr failed while checking 'hkps.pool.sks-keyservers.net': No name
    dirmngr[2004.0]: resolve_dns_addr failed while checking 'hkps.pool.sks-keyservers.net': No name
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'hufu.ki.iif.hu'
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'gozer.rediris.es'
    dirmngr[2004.0]: resolve_dns_addr failed while checking 'hkps.pool.sks-keyservers.net': Server indicated a failure
    dirmngr[2004.0]: resolve_dns_addr failed while checking 'hkps.pool.sks-keyservers.net': Server indicated a failure
    S PROGRESS tick ? 0 0
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'bone.digitalis.org' [already known]
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'ip-209-135-211-141.ragingwire.net'
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'hufu.ki.iif.hu' [already known]
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'gpg.NebrWesleyan.edu' [already known]
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'vsund.de'
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'gozer.rediris.es' [already known]
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'oteiza.siccegge.de' [already known]
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'ams.sks.heypete.com'
    dirmngr[2004.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net': 'host-37-191-238-78.lynet.no'
    S SOURCE https://ams.sks.heypete.com:443
    D -----BEGIN PGP PUBLIC KEY BLOCK-----%0AVersion: SKS 1.1.6%0AComment:Hostname: ams.sks.heypete.com%0A%0A
    ...
    OK
 -> bye
    OK closing connection
    $

--