On Mon, 4 May 1998, Anonymous wrote:
Actually, no. That was the example message from the first version
of the draft. Please repeat your analysis (with which I'm in
agreement) with the message from the most recent -02.txt draft:
-----BEGIN PGP MESSAGE-----
Version: OpenPGP 1.0
yCoBc07MUy9RSMyrzM9LVchOTS1QSFQoTk0uSgUKFuWX5qUoZKQWpdpzAQA=
=jYsF
-----END PGP MESSAGE-----
This one dearmors to:
000000 c8 2a 01 73 4e cc 53 2f 51 48 cc ab cc cf 4b 55
000010 c8 4e 4d 2d 50 48 54 28 4e 4d 2e 4a 05 0a 16 e5
000020 97 e6 a5 28 64 a4 16 a5 da 73 01 00
00002c
which is 0x2c bytes total, so there are exactly 0x2a bytes following the
0x2a (final-)packet-length byte.
This is the one I claim doesn't decompress to a valid OP packet.
You are correct. Decompression yields plaintext instead of a literal.
I think it was made with a version of my library demo program that can do
each step individually, and the enliteraling step was omitted.
A corrected version (using _CONSOLE as the name):
-----BEGIN PGP MESSAGE-----
Version: OpenPrivacy 0.99
yDgBO22WxBHv7O8X7O/jygAEzol56iUKiXmV+XmpCtmpqQUKiQrFqclFqUDBovzS
vBSFjNSiVHsuAA==
=njUN
-----END PGP MESSAGE-----