Gpg revocation anomaly

[Hauke Laging]

Am Fr 17.08.2012, 17:43:04 schrieb No such Client:

> # during import.... :
> 
> gpg --import testkey2.pub
> gpg: key FC736AA2: "testkey2" revocation certificate added
> gpg: key FC736AA2: "testkey2" 1 new signature
> gpg: Total number processed: 1
> gpg:         new signatures: 1
> gpg: public key 9AD09F2D is 57303581 seconds newer than the signature
> gpg: public key 0B12861B is 9237 seconds newer than the signature
> gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
> gpg: depth: 0  valid:  26  signed:  13  trust: 0-, 0q, 0n, 0m, 0f, 26u
> gpg: depth: 1  valid:  13  signed:   0  trust: 0-, 1q, 8n, 3m, 1f, 0u
> gpg: next trustdb check due at 2012-09-11

I think there are two problems:

a) This strange time problem. Try --ignore-time-conflict.

b) Have you imported the public key of testkey1 in your normal keyring? If not 
then the validity of the revocation signature cannot be checked.

Both reasons should make gpg ignore the revocation signature.

What is the output of gpg -vv --list-packets for the revocation signature 
file?


Hauke
-- 
☺
PGP: D44C 6A5B 71B0 427C CED3 025C BD7D 6D27 ECCB 5814
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 555 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20120817/60303bed/attachment.pgp>