Re: [Sks-devel] does merge works correctly on SKS

[Peter Palfrader]

On Sat, 06 Mar 2004, Roman Pavlik wrote:

> :public key packet:
>       version 4, algo 17, created 990764448, expires 0
>       pkey[0]: [1024 bits]
>       pkey[1]: [160 bits]
>       pkey[2]: [1023 bits]
>       pkey[3]: [1022 bits]
> :user ID packet: "Roman Pavlik <address@hidden>"
> :signature packet: algo 17, keyid EA9C66EAB9F8D6D9
>       version 4, created 1017556599, md5len 0, sigclass 13
>       digest algo 2, begin of digest 0d 5b
>       hashed subpkt 2 len 4 (sig created 2002-03-31)
>       hashed subpkt 11 len 4 (pref-sym-algos: 7 10 3 4)
>       hashed subpkt 21 len 2 (pref-hash-algos: 3 2)
>       hashed subpkt 22 len 2 (pref-zip-algos: 2 1)
>       hashed subpkt 23 len 1 (key server preferences: 80)
>       subpkt 16 len 8 (issuer key ID EA9C66EAB9F8D6D9)
>       subpkt 101 len 6 (experimental / private subpacket)
>       data: [160 bits]
>       data: [157 bits]
> 
> But PGP key from server differ:
> :public key packet:
>       version 4, algo 17, created 990764448, expires 0
>       pkey[0]: [1024 bits]
>       pkey[1]: [160 bits]
>       pkey[2]: [1023 bits]
>       pkey[3]: [1022 bits]
> :user ID packet: "Roman Pavlik <address@hidden>"
> :signature packet: algo 17, keyid EA9C66EAB9F8D6D9
>       version 4, created 1017556599, md5len 0, sigclass 13
>       digest algo 2, begin of digest 0d 5b
>       hashed subpkt 2 len 4 (sig created 2002-03-31)
>       hashed subpkt 11 len 4 (pref-sym-algos: 7 10 3 4)
>       hashed subpkt 21 len 2 (pref-hash-algos: 3 2)
>       hashed subpkt 22 len 2 (pref-zip-algos: 2 1)
>       hashed subpkt 23 len 1 (key server preferences: 80)
>       subpkt 16 len 8 (issuer key ID EA9C66EAB9F8D6D9)
>       data: [160 bits]
>       data: [157 bits]
> :signature packet: algo 17, keyid EA9C66EAB9F8D6D9
>       version 4, created 1017556599, md5len 0, sigclass 13
>       digest algo 2, begin of digest 0d 5b
>       hashed subpkt 2 len 4 (sig created 2002-03-31)
>       hashed subpkt 11 len 4 (pref-sym-algos: 7 10 3 4)
>       hashed subpkt 21 len 2 (pref-hash-algos: 3 2)
>       hashed subpkt 22 len 2 (pref-zip-algos: 2 1)
>       hashed subpkt 23 len 1 (key server preferences: 80)
>       subpkt 16 len 8 (issuer key ID EA9C66EAB9F8D6D9)
>       subpkt 101 len 6 (experimental / private subpacket)
^^^^^^^^^^^^^^^^^^^^^^^^ (missing above).
>       data: [160 bits]
>       data: [157 bits]
> 
> Why there are two signature packets with the same keyid on the SKS?
> Only answer I can find is that merge doesn't work correctly. 
> Any (other) idea?

One keyserver removed the 101 subpacket.  So the self signature packets
do differ.  If you look at F90F9FF1 it has 4 self signatures on some
packets.  1 is really different than the others, but the other 3 only
differ with existance or location of the 101 subpacket.

I am not sure what the right thing to do would be.

Peter
-- 
 PGP signed and encrypted  |  .''`.  ** Debian GNU/Linux **
    messages preferred.    | : :' :      The  universal
                           | `. `'      Operating System
 http://www.palfrader.org/ |   `-    http://www.debian.org/

signature.asc
Description: Digital signature