[Gpg4win-users-en] gpg4win 3.1.16 with updated GnuPG 2.2.32: No public key found despite having refreshed the keys
bernhard at intevation.de
Wed Dec 22 11:32:05 CET 2021
Am Mittwoch 22 Dezember 2021 02:11:28 schrieb David:
> I had the same problem yesterday and so I may be able to help here.
> *My fix was to reimport the key EF6E 286D DA85 EA2A 4BA7 DE68 4E2C 6E87
> 9329 8290 from a recent copy as I think it has been edited to extend the
> expiration date.*
> I cut and paste into GPA from
Looking at a more full version, e.g.
it seems is one one of the public keys that got flodded with
third-party signatures and they added a new subkey.
This will cause the problem when refreshing the key.
It seems the emerging new pubkeyserver do not carry the pubkey currently,
The a better alternative then using keys.openpgp.org is to use
WKD to get the pubkey directly from the Tor Project, e.g.
(The problem with keys.openpgp.org is that they valididate pubkeys, which aims
for being a central service and they do not serve the other pubkeys in a way
being compatible with the openpgp standard 4880.)
But WKD is more directy anyway, so you could use
gpg --auto-key-locate nodefault,wkd --locate-keys torbrowser at torproject.org
gpg --locate-keys torbrowser at torproject.org
in the command line.
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...
Size: 659 bytes
Desc: This is a digitally signed message part.
More information about the Gpg4win-users-en