GPG wants to check trustdb every day
Walt Mankowski
waltman at pobox.com
Mon Dec 27 14:43:43 CET 2004
On Mon, Dec 27, 2004 at 10:40:30AM +0000, Neil Williams wrote:
> When did you import 0x98645519?
I don't know how to determine that, but judging from the other keys
around it in the output of "gpg --list-keys" I'd say it was sometime
in 2000 or 2001. I've noticed those sorts of error messages before
but they never seemed to cause any problems.
>
> From the keyserver output, it would seem that there is an oddity with the
> signatures:
> pub 1024R/98645519 1998-10-14 Jeremy Blosser
> Key fingerprint = 1D D8 8E 3C 3E 19 74 EB 2F 70 EA 79 4B 50 D3 B5
> sig 0x10 98645519 1998-10-13 [selfsig]
> uid Jeremy Blosser
> sig 0x10 98645519 1998-10-13 [selfsig]
>
> Does removing this key eliminate the check-trustdb problem?
>
> Maybe if the keyholder edits the key (e.g. set the passphrase again (same one,
> just repeat it), his copy of gpg will put a new self-sig on the key to solve
> this problem?
>
> > As far as I know I haven't changed anything. /usr/bin/gpg was last
> > changed on 2004-02-23, and ~/.gnupg/options was changed on 2003-07-30.
> >
> > I've tried running "gpg --rebuild-keydb-caches" but that didn't help.
> > Anyone know what else might be causing this?
>
> I'd blame the key before gpg.
I'm doubtful, since it's been on my keyring for years without any
problem.
Walt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : /pipermail/attachments/20041227/8fa30629/attachment.bin
More information about the Gnupg-users
mailing list