[firstname.lastname@example.org: Creating things PGP 2 will read]
Wed, 12 May 1999 08:57:55 +0200
See GnuPG's README file: It is signed by GnuPG and PGP can handle it.
The trick is, that you can't pipe the input to gpg becuase gpg is then
forced to used partial length headers - something pgp 2 doesn't know
pgp --clearsign jnk
is allo need.
----- Forwarded message from Jason Gunthorpe <email@example.com> -----
Date: Wed, 12 May 1999 04:57:41 +0200
From: Jason Gunthorpe <firstname.lastname@example.org>
Subject: Creating things PGP 2 will read
X-Diagnostic: Not on the accept list
I have had excellent luck in making GPG (with the RSA and IDEA modules)
able to read PGP 2.6 signatures and encrypted messages. However, I have
never been able to get GPG to generate anything that PGP 2.6 will
understand :< The output from GPG works entirely fine with GPG itself.
Is there some manner of options that can make this work? I am using the
#cat jnk | gpg --rfc1991 --no-comment --clearsign > enc
And PGP gets as far as:
#cat enc | pgp
WARNING: Bad signature, doesn't match file contents!
Bad signature from user "Jason Gunthorpe <email@example.com>".
Signature made 1999/05/12 02:57 GMT using 1024-bit key, key ID 35261E21
So it understand the packet but I presume it must be hashing differently?
----- End forwarded message -----
Werner Koch at guug.de www.gnupg.org keyid 621CC013