Hi Werner! Werner Koch: > The attached patch fixes this problem.
Thanks for caring! I've tried rebuilding the package currently in sid with this patch applied, but it doesn't seem to be enough. The first --recv-keys triggers: Jan 02 13:36:33 dirmngr[8281]: DBG: dns: getsrv(_hkp._tcp.hkps.pool.sks-keyservers.net): Server indicated a failure Jan 02 13:36:33 dirmngr[8281]: command 'KS_GET' failed: Server indicated a failure <Unspecified source> Jan 02 13:36:33 dirmngr[8281]: DBG: chan_5 -> ERR 219 Server indicated a failure <Unspecified source> ... which is expected if querying 127.0.0.1, that doesn't support SRV records. And the next attempts, after manually telling dirmngr that my keyserver is alive: Jan 02 13:37:56 dirmngr[8281]: connection from process 8506 (1002:1002) Jan 02 13:37:56 dirmngr[8281]: DBG: chan_5 <- GETINFO version Jan 02 13:37:56 dirmngr[8281]: DBG: chan_5 -> D 2.1.17 Jan 02 13:37:56 dirmngr[8281]: DBG: chan_5 -> OK Jan 02 13:37:56 dirmngr[8281]: DBG: chan_5 <- KEYSERVER --clear hkps://hkps.pool.sks-keyservers.net Jan 02 13:37:56 dirmngr[8281]: DBG: chan_5 -> OK Jan 02 13:37:56 dirmngr[8281]: DBG: chan_5 <- KS_GET -- 0x7C84A74CFB12BC439E81BA78C92949B8A63BB098 Jan 02 13:37:57 dirmngr[8281]: DBG: dns: resolve_dns_name(hkps.pool.sks-keyservers.net): Success Jan 02 13:37:57 dirmngr[8281]: can't connect to 'hkps.pool.sks-keyservers.net': no IP address for host Jan 02 13:37:57 dirmngr[8281]: error connecting to 'https://hkps.pool.sks-keyservers.net:443': Unknown host Jan 02 13:37:57 dirmngr[8281]: marking host 'hkps.pool.sks-keyservers.net' as dead strace still seems to indicate that resolv.conf is read, and then 127.0.0.1 is queried. Cheers, -- intrigeri
