OpenPGP headers

Atom 'Smasher' atom at suspicious.org
Wed Aug 11 04:34:51 CEST 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, 11 Aug 2004, Simon Josefsson wrote:
> Atom 'Smasher' <atom at suspicious.org> writes:

> should be allowed?  Thus removing the need for OpenPGP-URL.  Hm.  Then
> the header could be called simply 'OpenPGP' which is neat.  E.g.:
>
> OpenPGP: id=B565716F; url=http://josefsson.org/key.txt; algo=1 (RSA); size=1280
>
> Where all of the following would be equally valid:
>
> OpenPGP: id=B565716F
> OpenPGP: url=http://josefsson.org/key.txt
> OpenPGP: id=B565716F; algo=1 (RSA); size=1280
> OpenPGP: url=http://josefsson.org/key.txt; algo=1 (RSA); size=1280
===================

i really like this...!

one header with 4 fields, each field is optional and MAY include human 
readable comments... so even this would be valid:
 	OpenPGP: id=0x12345678 (DSA/1024)
even though the algo and size cannot be parsed.

or this example:
 	OpenPGP: id=0x12345678 (This key is only used to
 		sign things when i'm at the office)

if someone feels inclined to identify their key using a short id, long id, 
or fingerprint, all are valid.

it may produce a header that isn't the most aesthetically pleasing, but it 
would be a single header that it both human and machine readable.... this 
is moving towards elegance!

i'll be re-reading rfc 2822, and then rewrite my draft accordingly...


> Btw, does 2440 specify an unambiguous value for 'size' for DSA,
> ElGamal, etc?
====================

not that i've found  :(


 	...atom

  _________________________________________
  PGP key - http://atom.smasher.org/pgp.txt
  762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
  -------------------------------------------------

 	"I would rather fail in a cause that will ultimately triumph
 	 than triumph in a cause that will ultimately fail."
 		-- Woodrow Wilson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.6 (FreeBSD)
Comment: What is this gibberish?
Comment: http://atom.smasher.org/links/#digital_signatures

iQEcBAEBCAAGBQJBGYXRAAoJEAx/d+cTpVciki8IAJY8LKRMYDqvxkv40IYHuO/Y
iKN/1s3zoNdOdK3w6HcCf7O4aqhpygoOhtIUJXyUWf18SycXaicLVoG0tjxmHid2
m7sLTAdG+m5Z/rCifftLUfg0dTB8kuQjCptnVp3lUypexgaIbhkkIN7Xwjpp9ded
h4JNzjWqTnzkZYS1ktPp8KR9kUHziAvAcXTouHxHXA7niueDA4mCz9Ao8GERW516
bu2EwtbVq74N9zNaMc6m2N702hdaZI4/K867GYoHv1V0MaUsd7dnFlcpaE//bYEl
uF50FcXskJRxu9tuMlal49A5Qw+30P65IosX2U3BScgSxuDEs/SkKh2I1gYNsuE=
=uXpe
-----END PGP SIGNATURE-----



More information about the Gnupg-devel mailing list