Page MenuHome GnuPG
Create Task
Maniphest T2968

gpg --search: Connection closed in DNS
Closed, ResolvedPublic
Actions

Description

On debian stretch "gpg --search" fails since gnupg2.1. All keyserver options are
disabled in gpg.conf.

$ gpg --version
gpg (GnuPG) 2.1.18
libgcrypt 1.7.6-beta
$ dirmngr --version
dirmngr (GnuPG) 2.1.18
$ gpg --search collective@riseup.net
gpg: error searching keyserver: Connection closed in DNS
gpg: keyserver search failed: Connection closed in DNS
$ gpg -vvv --debug-level guru --search collective@riseup.net
gpg: using character set 'utf-8'
gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat
trust hashing ipc clock lookup extprog
gpg: DBG: [not enabled in the source] start
gpg: DBG: chan_3 <- # Home: /home/kardan/.gnupg
gpg: DBG: chan_3 <- # Config: /home/kardan/.gnupg/dirmngr.conf
gpg: DBG: chan_3 <- OK Dirmngr 2.1.18 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_3 -> GETINFO version
gpg: DBG: chan_3 <- D 2.1.18
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KS_SEARCH -- collective@riseup.net
gpg: DBG: chan_3 <- ERR 167772876 Connection closed in DNS <Dirmngr>
gpg: error searching keyserver: Connection closed in DNS
gpg: keyserver search failed: Connection closed in DNS
gpg: DBG: chan_3 -> BYE
gpg: DBG: [not enabled in the source] stop
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0

outmix=0 getlvl1=0/0 getlvl2=0/0

gpg: secmem usage: 0/65536 bytes in 0 blocks

ii gnupg 2.1.18-3 i386
ii dirmngr 2.1.18-3 i386

Related Objects

Event Timeline

kardan added projects: dirmngr, Keyserver, gnupg, gnupg (gpg21), Debian, Bug Report.Feb 19 2017, 8:51 PM
kardan added a subscriber: kardan.
dkg added a subscriber: dkg.Feb 21 2017, 4:43 PM

Are you using tor? if so, is your tor daemon up and running, and actively
connecting to the outside world?

kardan added a comment.Mar 16 2017, 7:27 AM

I don't know why, it is not repdroducible anymore.

kardan closed this task as Resolved.Mar 16 2017, 7:27 AM
kardan claimed this task.
kardan added a comment.Mar 16 2017, 3:16 PM

I was able to reproduce it again. Maybe this bug depends on which keyserver in
the pool answers. The error is the same for Tor and non-Tor connections.

kardan reopened this task as Open.Mar 16 2017, 3:16 PM
• werner reassigned this task from kardan to justus.Mar 20 2017, 2:55 PM
• werner added a subscriber: justus.
• werner added a subscriber: • werner.Jun 23 2017, 5:11 PM

Any update on this?

elonsatoshi added a subscriber: elonsatoshi.EditedAug 27 2017, 4:58 PM

Well, I'm able to reproduce this issue on Parabola. I was also get a different error when I turn off my vpn: `server indicated a failure```, but now I get the dns error again.

elonsatoshi@tyger ~> gpg -vvv --debug-level guru --search elonsatoshi@riseup.net
gpg: using character set 'utf-8'
gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat trust hashing ipc clock lookup extprog
gpg: DBG: [not enabled in the source] start
gpg: DBG: chan_3 <- # Home: /home/elonsatoshi/.gnupg
gpg: DBG: chan_3 <- # Config: [none]
gpg: DBG: chan_3 <- OK Dirmngr 2.1.23 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_3 -> GETINFO version
gpg: DBG: chan_3 <- D 2.1.23
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KEYSERVER --clear hkps://pgp.mit.edu/
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KS_SEARCH -- elonsatoshi@riseup.net
gpg: DBG: chan_3 <- ERR 167772876 Connection closed in DNS <Dirmngr>
gpg: error searching keyserver: Connection closed in DNS
gpg: keyserver search failed: Connection closed in DNS
gpg: DBG: chan_3 -> BYE
gpg: DBG: [not enabled in the source] stop
gpg: keydb: handles=0 locks=0 parse=0 get=0
gpg:        build=0 update=0 insert=0 delete=0
gpg:        reset=0 found=0 not=0 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=0 cached=0 good=0 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks
elonsatoshi@tyger ~> sudo rc-service openvpn stop
[sudo] password for elonsatoshi: 
 * WARNING: openvpn is already stopped
elonsatoshi@tyger ~> pidof openvpn
elonsatoshi@tyger ~> gpg -vvv --debug-level guru --search elonsatoshi@riseup.net
gpg: using character set 'utf-8'
gpg: enabled debug flags: packet mpi crypto filter iobuf memory cache memstat trust hashing ipc clock lookup extprog
gpg: DBG: [not enabled in the source] start
gpg: DBG: chan_3 <- # Home: /home/elonsatoshi/.gnupg
gpg: DBG: chan_3 <- # Config: [none]
gpg: DBG: chan_3 <- OK Dirmngr 2.1.23 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_3 -> GETINFO version
gpg: DBG: chan_3 <- D 2.1.23
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KEYSERVER --clear hkps://pgp.mit.edu/
gpg: DBG: chan_3 <- OK
gpg: DBG: chan_3 -> KS_SEARCH -- elonsatoshi@riseup.net
gpg: DBG: chan_3 <- ERR 167772876 Connection closed in DNS <Dirmngr>
gpg: error searching keyserver: Connection closed in DNS
gpg: keyserver search failed: Connection closed in DNS
gpg: DBG: chan_3 -> BYE
gpg: DBG: [not enabled in the source] stop
gpg: keydb: handles=0 locks=0 parse=0 get=0
gpg:        build=0 update=0 insert=0 delete=0
gpg:        reset=0 found=0 not=0 cache=0 not=0
gpg: kid_not_found_cache: count=0 peak=0 flushes=0
gpg: sig_cache: total=0 cached=0 good=0 bad=0
gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
gpg: rndjent stat: collector=0x0000000000000000 calls=0 bytes=0
gpg: secmem usage: 0/32768 bytes in 0 blocks
• werner moved this task from gpg21 to gpg22 on the gnupg board.Oct 20 2017, 1:48 PM
• werner edited projects, added gnupg (gpg22); removed gnupg (gpg21), gnupg.
• werner removed justus as the assignee of this task.Oct 24 2017, 3:00 PM
elonsatoshi added a comment.Nov 19 2017, 4:48 AM

You know... I think connman and DNS have something to do with this. Connman does some weird DNS thing. And it auto-generates /etc/resolv.conf to use localhost as the DNS server.

• gniibe mentioned this in T4036: gnupg 2.2.9 release.Jun 20 2018, 8:23 AM
• werner added a project: Info Needed.Aug 29 2018, 2:53 PM

@elonsatoshi: Were you able to check this with 2.2.9 which has a fix for the resolver?

• werner closed this task as Resolved.Sep 11 2018, 10:34 AM
• werner claimed this task.

We assume that this has meanwhile been fixed.