vedaal@hush.com (vedaal@hush.com) writes:

>pgp 2.x _cannot_ handle signed and encrypted messages from gnupg,
>no matter what options are used,
>as there is a different sign and encrypt mechanism that gnupg uses,
>that can't be made to work with pgp2.x (even Disastry's)


Hmmph!

Here is a message, signed by my RSA key, and encrypted to key
0x71A7C295 with gnupg. The encrypt key was created in pgp-2.6.2. I
made the throw-away encryption key small (512 bits) since this is
only a demo.

The key is signed with my pgp2 key 0xE6D07471, which you should be
able to find on the keyservers. In my test, pgp-2.6.2 would not
decrypt unless I had that signing key on my keyring.

The keys to decrypt are below.

-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.3.91 (SunOS)

hIwD4dT8FObQdHEBBACbKn4OS2c58Z66J9M5Tc2LERyyOQFuJV y0zJeN7mvExwAb
c57vCNKzHOGJt77HyyLrJyYZQZw00iXPt3jAvFEjuSWTDxXVHJ UiqcgRJIna+lEb
CdeCJMAO9CqGTROzvGgiZgYJN0gCAW5bdedJnwWs5n3ax5hgXJ HxDJlnrQRLhYRM
Az+vz81xp8KVAQH/ey7hkikS1ti60dul+NPzBpsL0osEEAuZEAg6VP7Z4zowHplW
AtMjRP/6ZPv/u1Dg129U3bzE8GjokogYdLgtRKUBGYc50BlSuKM2M57A0JIJwG t9
a2/KBOOpfO05EBNQBcr/z3ZzoKDCPv/wFIFz2jbPZ/RKwgV9AtU1LyFZhfCMBmKh
w6k/xT209x65J74I3dE41q+876t8UtvPBd7ZXuAGrPFJN5TcaUSQDQ wohUNFSfL2
iv0zmXjEzIw8nzi/8X45XQ5JuZfMtasrUN56SZMZSZMLExpEMcObZv6Ivnv19Xc/
e4uBW6a6hby0tvTTsuD8eZ9DkV+Ur0y1r8YFKURFq0/1GpV8JxrgSL+HtAx0gn8J
4wpLL1M1xwmAagaDXKge18ePOmndEA8cCaf8LffTwuFAXaU1DC NzUVO1MUZVE+Pi
2128xQ4uzRo4m8WxKGpFGKj7TB7hkc/v
=x60R
-----END PGP MESSAGE-----

Hmm, I see that I used gnupg-1.3.91 for that. But I could have done
the same with gnupg-1.2.x (for various x).

Here is the public key for 0x71A7C295

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2

mQBNA0F1IeAAAAECAMdB2oToJo4Q+5NpPII5r1McHd7XARGuu0 M+NU84WyxQl8Lj
dXFmYwanx8R07FGJsfxWz6IpWJ/3P6/PzXGnwpUABRG0GURlbW8ga2V5IDxub2Jv
ZHlAbm93aGVyZT6JAFUDBRBBdSIrP6/PzXGnwpUBAa4LAf95ezhFm5sKHdxNmtcw
JysO7appOGO7L3PTL45/Lq8cPaOoLHYuZN3yHCd4Ytl1LzjOkdRZ4eZ82Pr0gtSB
okcB
=FKk9
-----END PGP PUBLIC KEY BLOCK-----

And here is the private key for 0x71A7C295

It looks funny -- like a message rather than a key. That's the
way pgp-2.6.2 exports private keys. Save it to a file, and use

pgp file

to import to your secring.pgp

-----BEGIN PGP MESSAGE-----
Version: 2.6.2

lQD4A0F1IeAAAAECAMdB2oToJo4Q+5NpPII5r1McHd7XARGuu0 M+NU84WyxQl8Lj
dXFmYwanx8R07FGJsfxWz6IpWJ/3P6/PzXGnwpUABREAAf4u4lGIrxghbWhe65XE
Sc7mYPf4MpbW++/TliqpOm/OMKmaPSleZvVN4w+W3y/Rd9CBdy9y5zaVzHT20fxr
y/IhAQDIXHhXrMJZgW2xuRmTX8vc0ui11mZsLrJjOxhoUJ9SgwEA/pbnLfNudvo1
E8omzbeAnwMzkCNsRHSf61u69FblqwcBAOtAhPo/ql5oG1mUwE5mrzBaB+y6HVYh
vuGMKEcNWK89VKy0GURlbW8ga2V5IDxub2JvZHlAbm93aGVyZT 4=
=s4ug
-----END PGP MESSAGE-----

There wasn't a single command I used to encrypt and sign with gnupg.
I had to use a sequence of 4 commands to build the message in the
needed format. But gnupg does make it possible. It also curses you
when doing this.

I won't sign this post, to avoid confusing the jumble of pgp
components. On second thoughts, I will sign with the usenet control
message format signature that appears only in the headers. You might
have difficulty verifying that signature.