Keys cannot be refreshed via "gpg2 --refresh-keys"

Bug #1623159 reported by Colan Schwartz on 2016-09-13
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnupg2 (Ubuntu)

Bug Description

gpg2 --refresh-keys yields the following:

gpg: keyserver refresh failed: No keyserver available

However, I have everything set up in dirmngr.conf:

keyserver hkp://jirk5u4osbsr34t5.onion
keyserver hkps://
hkp-cacert /home/colan/.gnupg/sks-keyservers.netCA.pem

...and dirmngr can find it:

colan@snake[Tue 13 14:30]% dirmngr
dirmngr[26401.0]: permanently loaded certificates: 0
dirmngr[26401.0]: runtime cached certificates: 0
# Home: ~/.gnupg
# Config: /home/colan/.gnupg/dirmngr.conf
OK Dirmngr 2.1.11 at your service

Looks like gpg2 isn't grabbing the correct information from the response as here's what's happening with debugging turned on:

colan@snake[Tue 13 14:30]% gpg2 --refresh-keys --debug-all
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_6 -> GETINFO version
gpg: DBG: chan_6 <- D 2.1.11
gpg: DBG: chan_6 <- OK
gpg: DBG: chan_6 -> KEYSERVER
gpg: DBG: chan_6 <- OK
gpg: keyserver refresh failed: No keyserver available
gpg: DBG: chan_6 -> BYE

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnupg2 2.1.11-6ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Sep 13 14:31:34 2016
EcryptfsInUse: Yes
SourcePackage: gnupg2
UpgradeStatus: No upgrade log present (probably fresh install)

Colan Schwartz (colan) wrote :
Changed in gnupg2:
status: Unknown → New
Changed in gnupg2:
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnupg2 (Ubuntu):
status: New → Confirmed
Changed in gnupg2 (Ubuntu):
importance: Undecided → High
tags: added: yakkety
Marcus Hoffmann (bubuiic) wrote :

This now hit me on artful, gpg is pretty much unusable right now.

(I didn't mean to change the bugs settings...)

information type: Public → Public Security
information type: Public Security → Public
Marcus Hoffmann (bubuiic) wrote :

Building and installing upstream gpg (v2.2.2) fixes the problem

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.