HOW to upgrade: 2.0.22 --> 2.3.3 ???

[Björn Persson]

Mike Schleif wrote:
> ownertrust.txt:
> 41261F6446B51FDBD18FDDF8C4D62F13571F553F:5:

This is how much you trust the owner of that key when they sign other
keys. Before you can trust the owner, you need to know who the key
belongs to.

> 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.

> Is the _only_ solution to convert ALL keys to ultimate (6)?

You're supposed to verify that the key really does belong to
"FISERV-SFG-NA-PROD-GPG-2K-23-193-01", and not to some attacker who is
trying to fool you. After you have verified this, you assure it by
signing the key with your own key. Then GPG will know that the key
belongs to the named user.

Björn Persson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signatur
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20241010/3db2ef2b/attachment.sig>