Re: [PLUG] GnuPG 1.2.1 trustdb checks for every pubkey import?

David Shaw on 2003年2月27日 01:01:07 -0500


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] GnuPG 1.2.1 trustdb checks for every pubkey import?


On Thu, Feb 27, 2003 at 12:32:19AM -0500, gabriel rosenkoetter wrote:
> This behavior showed up when I upgraded from 1.0.7 to 1.2.1. It had
> also showed up when I'd switched to 1.0.7 (or maybe to 1.0.6?),
> which I was warned about in the release notes, and (at the time) I
> backed my trustdb up and did whatever I was told to it after the
> upgrade (I think it was just --rebuild-keydb-caches, but maybe it
> was --update-trustdb). I've also recently done a --update-trustdb
> pass which involved setting ownertrust values for a lot of keyids,
> but I've run --check-trustdb countless times since then without any
> change in its performance.
Try running "gpg --no-sig-cache --rebuild-keydb-caches". It'll take a
long time. I suspect you have some uncached signatures and/or
uncached Elgamal signatures (worse) on your keyring.
The next version of GnuPG (1.2.2) takes extreme care to always cache
every possible signature when importing a key.
David

Attachment: pgp12WgOLELhn.pgp
Description: PGP signature




AltStyle によって変換されたページ (->オリジナル) /