Question about --rebuild-keydb-caches

[Michael Nahrath]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig58B1961704ED22B370E96E0F
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Ingo Klöcker wrote:

> On Sunday 20 April 2003 16:22, Michael Nahrath wrote:
> 
>>Ingo Klöcker wrote:
>>
>>>>time gpg --check-trustdb

>>Did you try this a second time as well?

> Yes, I ran "time gpg --check-trustdb" twice. Same result.

Sorry, I quoted the wrong line.

I meant "Did you run 'time gpg --rebuild-keydb-caches' for a second time?"

But manwhile you have run all the extended tests that I intended to suggest :)

> # gpg --list-keys | egrep pub\ \ ....G
> pub  4096G/DEADBEEF
> 
> So there is only one of those keys in my keyring.

I guess "DEADBEAF" stands for 10F4B2AA.

I had a problem with that key earlier and braught it to this list on 2002-12-04.

David Shaw explained then:

>> But before deleting them those 2 signatures seem to have corrupted my
>> whole keyring.
>
> Not corrupted.  David's key has several user ID revocations on it.
> Elgamal is a very slow signing algorithm, and validating those
> revocation self-signatures takes time.
>
> When you deleted one of them, you caused the signature cache to be
> updated, so the sigs didn't need to be checked again.  You could have
> deleted anything from that key or run --rebuild-keydb-caches and
> gotten the same result.
>
> When GnuPG imports a new key, it automatically caches signatures, but
> does not cache user ID revocations.

HTH,
Greeting, Michi

--------------enig58B1961704ED22B370E96E0F
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2rc2 (Darwin)
Comment: http://www.biglumber.com/x/web?qs=0x9A4C704C

iEYEARECAAYFAj6jsCAACgkQ19dRf5pMcEydNwCg+sK5uUAxNLB+iOyVp+8plD1B
yusAoKf/0O7yOK5M6MNNTjb6EUj5MXfL
=lFgL
-----END PGP SIGNATURE-----

--------------enig58B1961704ED22B370E96E0F--