GPG key not fully accepted by public key servers

[Stefan H. Holek]

On Mon, 18 Dec 2000 lewis@sistina.com wrote:

> Ok, I'm confused (sorry...I feel really stupid) but what do I do with this
> information.  Here's the output from the key I grabbed from pgp.ai.mit.edu.

No reason to feel stupid here! And nothing much you can do either. As of
now you should not use pks-type keyservers if you have multiple
subkeys. Distribute your public key directly by e.g. linking to it from
your webpage.


> ~> gpg --list-packets test.asc                         Mon 12.18 10:38
> :public key packet:
>         version 4, algo 17, created 974309008, expires 0
>         pkey[0]: [1024 bits]
>         pkey[1]: [160 bits]
>         pkey[2]: [1016 bits]
>         pkey[3]: [1022 bits]
> :user ID packet: "AJ Lewis (Roadrunner) <lewis@sistina.com>"
> :signature packet: algo 17, keyid 941E126100292648
>         version 4, created 974309008, md5len 0, sigclass 13
>         digest algo 2, begin of digest f3 29
>         hashed subpkt 2 len 5 (sig created 2000-11-15)
>         hashed subpkt 11 len 5 (pref-sym-algos: 7 10 3 4)
>         hashed subpkt 21 len 3 (pref-hash-algos: 3 2)
>         hashed subpkt 22 len 3 (pref-zip-algos: 2 1)
>         hashed subpkt 23 len 2 (key server preferences)
>         subpkt 16 len 9 (issuer key ID 941E126100292648)
>         data: [160 bits]
>         data: [156 bits]
> :user ID packet: "AJ Lewis <lewi0235@tc.umn.edu>"
> :signature packet: algo 17, keyid 941E126100292648
>         version 4, created 975593280, md5len 0, sigclass 13
>         digest algo 2, begin of digest d1 be
>         hashed subpkt 2 len 5 (sig created 2000-11-30)
>         hashed subpkt 11 len 5 (pref-sym-algos: 7 10 3 4)
>         hashed subpkt 21 len 3 (pref-hash-algos: 3 2)
>         hashed subpkt 22 len 3 (pref-zip-algos: 2 1)
>         hashed subpkt 23 len 2 (key server preferences)
>         subpkt 16 len 9 (issuer key ID 941E126100292648)
>         data: [158 bits]
>         data: [159 bits]
> :public sub key packet:
>         version 4, algo 16, created 974309011, expires 0
>         pkey[0]: [1024 bits]
>         pkey[1]: [3 bits]
>         pkey[2]: [1023 bits]

>>>>>>>>> HERE SHOULD BE A BINDING SIGNATURE <<<<<<<<<<<

> :public sub key packet:
>         version 4, algo 17, created 974309312, expires 0
>         pkey[0]: [1024 bits]
>         pkey[1]: [160 bits]
>         pkey[2]: [1023 bits]
>         pkey[3]: [1021 bits]
> :signature packet: algo 17, keyid 941E126100292648
>         version 4, created 974310923, md5len 0, sigclass 18
>         digest algo 2, begin of digest d6 95
>         hashed subpkt 2 len 5 (sig created 2000-11-15)
>         hashed subpkt 9 len 5 (key expires after 180d0h31m)
>         subpkt 16 len 9 (issuer key ID 941E126100292648)
>         data: [158 bits]
>         data: [160 bits]

Regards,
Stefan

-- 
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of  "unsubscribe"  to gnupg-users-request@gnupg.org