Problems with --check-trustdb in 1.3.93 on Windows

John Clizbe JPClizbe at
Thu Dec 16 04:03:05 CET 2004

Hash: SHA1

bash-2.05b$ gpg --version
gpg (GnuPG) 1.3.93

bash-2.05b$ time gpg --check-trustdb
<warning snipped>
gpg: renaming `C:/Documents and Settings/jpclizbe/Application
Data/GnuPG\pubring.tmp' to `C:/Documents and Settings/jpclizbe/Application
Data/GnuPG\pubring.gpg' failed: Permission denied
gpg: failed to rebuild keyring cache: file rename error
gpg: can't open `C:/Documents and Settings/jpclizbe/Application
gpg: keydb_search failed: file open error
gpg: validate_key_list failed

real    19m45.546s
user    0m0.020s
sys     0m0.020s

pubring.gpg was renamed to pubring.bak, but pubring.tmp was left as it
was. This was almost 20 minutes just for the cache rebuild, not even the
trust check.

bash-2.05b$ head/gpg --version
gpg (GnuPG) 1.3.93-cvs-2004-12-11

bash-2.05b$ time head/gpg --check-trustdb
<warning snipped>
gpg: renaming `C:/Documents and Settings/jpclizbe/Application
Data/GnuPG\pubring.gpg' to `C:/Documents and Settings/jpclizbe/Application
Data/GnuPG\pubring.bak' failed: Permission denied
gpg: failed to rebuild keyring cache: file rename error
gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model
gpg: depth: 0  valid:  36  signed: 429  trust: 0-, 0q, 0n, 0m, 0f, 36u
gpg: depth: 1  valid: 429  signed: 162  trust: 0-, 363q, 1n, 8m, 57f, 0u
gpg: depth: 2  valid:  64  signed:  60  trust: 0-, 58q, 0n, 3m, 3f, 0u
gpg: depth: 3  valid:   4  signed:  13  trust: 0-, 3q, 0n, 1m, 0f, 0u
gpg: next trustdb check due at 2004-12-23

real    37m14.658s
user    0m0.010s
sys     0m0.060s

In 1.3.93-cvs from this last weekend, the first rename failed and allowed
the check-trustdb to run. Please note the time taken.

Compare the time taken with 1.2.x:

bash-2.05b$ stable/gpg --version
gpg (GnuPG) 1.2.7-cvs-2004-12-11

bash-2.05b$ time stable/gpg --check-trustdb
gpg: checking at depth 0 signed=444 ot(-/q/n/m/f/u)=0/0/0/0/0/36
gpg: checking at depth 1 signed=172 ot(-/q/n/m/f/u)=0/377/1/9/57/0
gpg: checking at depth 2 signed=66 ot(-/q/n/m/f/u)=0/67/0/5/3/0
gpg: checking at depth 3 signed=9 ot(-/q/n/m/f/u)=0/3/0/0/0/0
gpg: next trustdb check due at 2004-12-23

real    0m19.438s
user    0m0.040s
sys     0m0.020s
bash-2.05b$ 1.2.6/gpg --version
gpg (GnuPG) 1.2.6

bash-2.05b$ time 1.2.6/gpg --check-trustdb
gpg: next trustdb check due at 2004-12-23

real    0m18.455s
user    0m0.010s
sys     0m0.020s

Checking the trustdb takes < 20 sec in 1.2.x but nearly 40 minutes in
1.3.93? OUCH!  Can this be worked on before 1.4?

- --
John P. Clizbe                   Inet:   JPClizbe(a)comcast DOT nyet
Golden Bear Networks             PGP/GPG KeyID: 0x608D2A10
"Be who you are and say what you feel because those who mind don't matter
and those who matter don't mind." - Dr Seuss, "Oh the Places You'll Go"
Version: GnuPG v1.3.93 (Windows 2000 SP4)
Comment: When cryptography is outlawed, b25seSBvdXRsYXdzIHdpbGwgdXNlIG
Comment: Annoy John Asscraft -- Use Strong Encryption.
Comment: It's YOUR right - for the time being.
Comment: Using GnuPG with Mozilla -


More information about the Gnupg-devel mailing list