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

To Damon damon.tu at outlook.com
Thu Jun 26 09:39:27 CEST 2025


I've tried to fix the trustdb following the recommended steps (exporting ownertrust, deleting trustdb.gpg, and importing ownertrust), but the issue still persists.
When I run gpg --list-secret-keys --with-fingerprint --with-keygrip, I see the following warning:

gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr: 51f9e32f62fa6745c5cb09c2412a0000
gpg: Note: ultimately trusted key 0000000000000000 not found
gpg: no ultimately trusted keys found

And when trying to sign:

echo "test" | gpg --clear-sign --user 412A000000000000

I get:

gpg: WARNING: recipients (-r) given without using public key encryption
gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr: 51f9e32f62fa6745c5cb09c2412a0000

It seems like the key is still missing or not trusted properly. Any ideas on what else I can try?


> On 25 Jun 2025, at 23:50, Werner Koch <wk at gnupg.org> wrote:
> 
> Hi!
> 
>>>> gpg: DBG: Oops: keyid_from_fingerprint: no pubkey; fpr:
>>>> 51f9e32f62fa6745c5cb09c2412a0000
> 
> The trustdb is probably corrupt.  Try this:
> 
> $ gpg --fix-trustdb
> gpg: You may try to re-create the trustdb using the commands:
> gpg:   cd ~/.gnupg
> gpg:   gpg --export-ownertrust > otrust.tmp
> gpg:   rm trustdb.gpg
> gpg:   gpg --import-ownertrust < otrust.tmp
> 
> 
> Shalom-Salam,
> 
>   Werner
> 
> -- 
> The pioneers of a warless world are the youth that
> refuse military service.             - A. Einstein




More information about the Gnupg-users mailing list