HOW to upgrade: 2.0.22 --> 2.3.3 ???
Jacob Bachmeyer
jcb62281 at gmail.com
Sun Oct 13 04:36:54 CEST 2024
On 10/10/24 10:09, Björn Persson wrote:
> Mike Schleif wrote:
> [...]
>> encryption error:
>> gpg: 9B51B2A5C71BDCEC: There is no assurance this key belongs to the named
>> user
> Such assurance is provided by signing the key. Maybe the signatures
> have been lost somehow, or the key that signed all the other keys is
> missing or untrusted, or you never signed the keys in the first place.
> Use --list-sigs to see what signatures exist. Then use --check-sigs to
> see whether the signatures are valid.
The thought occurs to me: we already know that this user has a bunch of
PGP2 keys in their keyring. Could the local signatures intended to
validate trust on other keys have been from now-unusable PGP2 keys?
-- Jacob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20241012/1767d341/attachment.html>
More information about the Gnupg-users
mailing list