Trust assignment fails for key with fingerprint ending in multiple zero blocks

[Andrew Gallagher]

On 13 Jun 2025, at 15:29, To Damon <damon.tu at outlook.com> wrote:
> 
>> gpg --list-secret-keys --with-fingerprint
> gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr: 51f9e32f62fa6745c5cb09c2412a0000
> gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr: 577e8f3f61625918c9c53c226b335000
> gpg: key 0000000000000000 occurs more than once in the trustdb
> gpg: checking the trustdb
> gpg: Note: ultimately trusted key 0000000000000000 not found
> gpg: no ultimately trusted keys found
> /home/user/.gnupg/pubring.kbx

This looks like there is a second issue, which is that the trustdb was updated with a null fingerprint or long keyID, twice. Not clear from the outside whether this is a related bug or independent, but it all seems to indicate a baked-in assumption that fingerprints will never have a large number of trailing zeros...

A

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250613/a2625047/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20250613/a2625047/attachment.sig>