[SOLVED] gpg: No keyserver available

[sdauth]

Hello,
I was trying to verify a signature for an old vlc version and I received this message :

Code: Select all

gpg: keyserver refresh failed: No keyserver available

After adding one of the following to : ~/.gnupg/gpg.conf

Code: Select all

keyserver hkps://keys.openpgp.org
keyserver hkps://keyserver.ubuntu.com

gpg --refresh-keys & gpg --recv-keys work again.
Then after importing the id, I'm able to verify the signature (although expired of course)

Code: Select all

gpg --verify vlc-2.1.3-win64.exe.asc vlc-2.1.3-win64.exe 
gpg: Signature made Fri Jan 31 12:16:23 2014 CET
gpg:                using DSA key 7180713BE58D1ADC
gpg: Good signature from "VideoLAN Release Signing Key (2018)" [expired]
gpg:                 aka "VideoLAN Release Signing Key (2013)" [expired]
gpg:                 aka "VideoLAN Release Signing Key (2015)" [expired]
gpg:                 aka "VideoLAN Release Signing Key (2014)" [expired]
gpg:                 aka "VideoLAN Release Signing Key (2016)" [expired]
gpg:                 aka "VideoLAN Release Signing Key (2017)" [expired]
gpg: Note: This key has expired!
      65F7C6B4206BD057A7EB73787180713BE58D1ADC

Anyway, I would like to know why do I have to manually add the keyserver line to my ~/.gnupg/gpg.conf.
I don't remember adding that and it worked fine for years without it. (the only line in this file was "use-agent")
I assumed it used hkps://keys.openpgp.org or something else by default.

[sdauth]

I found this relevant information in dirmngr manual :

Code: Select all

--keyserver
[...]
There is no default keyserver since version 2.5.3.
[...]

2.5.x series was stabilized a few months ago.
I admit I don't use gnupg very often (refreshing keys included) so it is very possible I notice that just now.