SOLVED (was: Re: strange error message, how to delete key 0x00000000)
telegraph at gmx.net
Sat Aug 20 18:05:17 CEST 2016
* Ben McGinnes <ben at adversary.org> [20. Aug. 2016]:
> On Fri, Aug 19, 2016 at 09:16:47PM +0200, Gregor Zattler wrote:
>> Thanks for your answer but in my case this seems not to be the
>> cause: I did a
>> gpg --list-public-keys |sed -e "s/ //g"|grep 000
>> gpg --fingerprint --list-public-keys |sed -e "s/ //g"|grep 000
>> and there are no keys with key ids or fingerprints ending in
>> more than two zeros.
>> Any other ideas?
> You may have had them in the past and the entry is still in the
This was it. Amazing numbers of key fingerprints ending in at
least 8 zeros.
> So deleting it and forcing a rebuild (you can always move
> the old one somewhere else instead) should recreate the thing without
> those errors.
Instead I did gpg --export-ownertrust, grep -v 00000000: and
imported the result, thus I did not loose my ownertrust settings
(e.g. which keys are mine = ultimate trusted).
Thanks for your help, Gregor
-... --- .-. . -.. ..--.. ...-.-
More information about the Gnupg-users