This has been an ongoing problem after the yang merge On Tue, Jun 24, 2025 at 4:05 AM To Damon via Gnupg-users < [email protected]> wrote:
> gpg (GnuPG) 2.4.8 still has these issues. > > > Hi Werner Koch, would you mind taking a look at this issue when you have a > moment? > > > > On 13 Jun 2025, at 22:34, Andrew Gallagher <[email protected]> wrote: > > > > On 13 Jun 2025, at 15:29, To Damon <[email protected]> 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 > > > > > _______________________________________________ > Gnupg-users mailing list > [email protected] > https://lists.gnupg.org/mailman/listinfo/gnupg-users >
_______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users
