[Sks-devel] Re: Time conflicts not checked on subkey signatures?

[Jason Harris]

On Fri, Nov 12, 2004 at 12:41:11PM +0100, Holger Sesterhenn wrote:

> I have done some research on how gnupg handles time conflicts between
> signature packets and public key packets/public subkey packets.

> You can see the problem with this key:

> pub:r:1024:17:131E92BF5A16ADD7:936832137:::-:::sca:
> fpr:::::::::02A3BC00358327E518CEA199131E92BF5A16ADD7:
> rev:!::17:131E92BF5A16ADD7:949365009::::RavingCow
> <address@hidden>:20x:
> uid:r::::942521984::9AAA48F52CA77FF628A75CB8BD913287A0DCBD68::RavingCow
> <address@hidden>:
> sig:?::17:F8601C136A6CF305:943903355:::::10x:
> rev:%::17:131E92BF5A16ADD7:943631147::::[unknown signature class] :28x:
> rev:%::17:131E92BF5A16ADD7:944264133::::[unknown signature class] :28x:

> Key fetched from hkp://subkeys.pgp.net yesterday.

> Any comments?

[None on the timestamp conflicts, but...]
SKS (and the public LDAP keyservers) allow subkey revocation signatures
(0x28) on userids, which is not RFC-compliant.

-- 
Jason Harris           |  NIC:  JH329, PGP:  This _is_ PGP-signed, isn't it?
address@hidden _|_ web:  http://keyserver.kjsl.com/~jharris/
          Got photons?   (TM), (C) 2004

pgp1Q4NRH7Z3M.pgp
Description: PGP signature