[Gpg4win-users-en] gpg4win 3.1.16 with updated GnuPG 2.2.32: No public key found despite having refreshed the keys

[Bernhard Reiter]

Hello Stella,

Am Mittwoch 22 Dezember 2021 12:17:45 schrieb Stella Ashburne:
> Thanks for taking the time to write a rather lengthy reply and I appreciate
> your effort.

thanks for your interest in Gpg4win/GnuPG.

> May I conclude that gpg4win is unable to cope with the scenario that you
> described? In any case, Debian 11 is able to refresh Tor's sub-keys without
> having to use WKD.

That is only half of the story.
Debian decided to use a central pubkey server by default,
in this case it is an advantage, but it has other drawbacks,
which is Gpg4win has decided against this default.
Most people think that WKD is a preferred solution to get public keys,
as it carries a bit of trust, which pubkeyservers do not.
Debian may also have done something else, I'm not sure why it worked for your 
there.

For Gpg4win 3.3.16 you'd need to use a second installer to get a newer GnuPG 
version as well for some tls connections to work. Or you get the fresh 
4.0.0. ;)

> It's not just keys.openpgp.org. I have tried at least six public keyservers
> without success.

After the breakdown of the old SKS keyserver network, a new one is just 
building up and does not yet have the old functionality.
(The main reason is that a new software has to be developed.)

> Best wishes of the season.

To you and everyone, too! :)
Bernhard

-- 
www.intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.wald.intevation.org/pipermail/gpg4win-users-en/attachments/20211222/fcf3914c/attachment.sig>