Page MenuHome GnuPG

GnuPG unable to interact with any keyserver throwing a "Not enabled" error
Closed, ResolvedPublic

Description

Using Arch Linux after a recent update to GnuPG when I try to interact with a keyserver (like fetching a key or refreshing keys), gpg throws a "Not enabled" error. While using --recv-key fails I can download a public key from a keyserver and use the --import flag with no problem so it is just when gpg is trying to work with a keyserver. I did try restarting dirmngr and gpg-agent to no avail.

Example output:

[~]─> gpg -vvv --refresh-keys
gpg: using character set 'utf-8'
gpg: refreshing 61 keys from hkps://keys.openpgp.org
gpg: keyserver refresh failed: Not enabled

dirmngr.conf:

gpg-agent.conf:

gpg.conf:

Details

Version
gpg (GnuPG) 2.2.39 libgcrypt 1.10.1-unknown

Event Timeline

I suspect that this has to do with your usage of tor (or gpg thinking that you use tor) because in dirmngr/dns-stuff.c I found

if (tor_mode)
  return gpg_error (GPG_ERR_NOT_ENABLED);

and all other places returning GPG_ERR_NOT_ENABLED seem to be related to S/MIME.

The use of

   hkp-cacert /usr/share/gnupg/sks-keyservers.netCA.pem

does not make any sense - that keyserver network has been shutddown and the certs won't work. anymore. Also the use of the standard-resolver is not a good idea because it does not work with Tor.

Also the use of the standard-resolver is not a good idea because it does not work with Tor.

It seems that was precisely the issue, sorry for the noise, I just couldn't find anything when I was searching the error message and didn't get any help on the Arch forums.

werner claimed this task.