On Tue, Nov 15, 2022 at 1:01 PM DdB <debianl...@potentially-spam.de-bruyn.de> wrote: > ... > i just experienced the same problem, same difficulty understanding the > man pages. Googling suggested to try a different keyserver. > I had to try several ... until i found one, that succeeded. > Apparently, the cause was found to be in the rules in place at the > servers. Some do no longer allow connections from sources without > self-signed pubkeys.
Yes, the key server pools are a mess. Part of it is because of Europe and GPPR. And the GnuPG folks have not done a good job updating the server code to meet the demands of the current landscape. I just shake my head in disbelief at what things have come to. It makes me want to unsubscribe from the GnuPG mailing lists... For example, from "keyserver receive failed: No name - for gpg --keyserver hkp://pool.sks-keyservers.net," https://lists.gnupg.org/pipermail/gnupg-users/2021-June/065261.html: The keyserver *pools* at sks-keyservers.net are no longer maintained for legal reasons. sks-keyservers.net was receiving GDPR requests, e.g. for RTBF [Right to be Forgotten], that it could not satisfy because the pools had no formal structure that could compel individual operators to comply with legal requests. Or, more discussions at https://www.google.com/search?q=keyserver+gdpr+site:lists.gnupg.org/pipermail/gnupg-users > But just adding the corresponding switch did not > help either. i had to find a server with an older config in place (like > ubuntu's). It's not you. The whole key server architecture is a mess nowadays. Jeff
