----- Original Message -----
From: "Werner Koch" <wk(_at_)gnupg(_dot_)org>
To: "Michael Young" <mwy-opgp97(_at_)the-youngs(_dot_)org>
Cc: <ietf-openpgp(_at_)imc(_dot_)org>
Sent: Wednesday, November 07, 2001 3:10 AM
Subject: Re: Parser abilities, and MDCs (Re: pointers to openpgp-interop
knowledge base?)
On Tue, 6 Nov 2001 23:17:56 -0500, Michael Young said:
answer. The issue was that GnuPG used an old-style indeterminate-length
packet for the plaintext before the MDC (see my message of August 23
But only if the plaintext is a compressed packet - right?
Werner
----- Original Message -----
From: "Werner Koch" <wk(_at_)gnupg(_dot_)org>
To: "Michael Young" <mwy-opgp97(_at_)the-youngs(_dot_)org>
Cc: <ietf-openpgp(_at_)imc(_dot_)org>
Sent: Wednesday, November 07, 2001 3:10 AM
Subject: Re: Parser abilities, and MDCs (Re: pointers to openpgp-interop
knowledge base?)
On Tue, 6 Nov 2001 23:17:56 -0500, Michael Young said:
answer. The issue was that GnuPG used an old-style indeterminate-length
packet for the plaintext before the MDC (see my message of August 23
But only if the plaintext is a compressed packet - right?
Werner
here is the url for the pgpdump web interface:
http://xdv.org/pgpdump/
here is the output for a message encrypted to an rsa key using gpg with
twofish as the algorithm:
PGPdump Results
Old: Public-Key Encrypted Session Key Packet(tag 1)(268 bytes)
New version(3) Key ID - f1 56 64 88 f7 7a ff 7b
Pub alg - RSA Encrypt or Sign(pub 1) RSA m^e mod n(2047 bits) -
78 02 54 44 fd 0b ec 0d 44 de 38 f8 95 f4 8d 89 0a 92 4a 47 4e f8 84 55 38
47 24 1a 3e 91 36 9f 72 32 21 54 43
f5 8b 4f be 1d ce 4c ec ac 87 89 85 f0 ae 2c a7 48 c8 e0 31 aa 42 88 68 41
51 56 84 6b bc 0a a1 9d 50 9b f8 7b 35 96 82 d7 9b 77 e6 95 b1 83 77 13 f2
bb c1 0b 28 9a e8 f9 ac 09 10 8d 93 84 92 5b 95 8c 7a a9 43 44 6d 38 a7 40
46 ef a6 86 2c bc 1c ae 2b 27 0d 48 34 d9 c3 89 d3 7b ef a9 b3 b7 dd 9d 87
80 30 26 8f b1 0d a6 a7 ba d0 aa 6c 3e 76 6d 82 ac 72 88 14 eb 90 8f 8e b8
29 bf ed 5a 07 46 93 02 ae 0e d4 46 3f df 6d 29 6b 70 70 a6 20 8a 95 83 4c
dc 7e 69 e9 69 56 a1 a6 8d fd ab 79 38 1d 93 da b8 1f d1 78 84 84 7b 48 74
d8 66 94 64 5d 8a 88 61 fb 14 de ba 4e 33 1c 6f ba 84 70 02 28 11 4f 05 ba
7d 4f 2e c6 f4 92 7a 99 cc 5d e6 98 e3 4f 24 7c df f9 57
-> m = sym alg(1 byte) + checksum(2 bytes) + PKCS-1 block type 02
New: Symmetrically Encrypted and MDC Packet(tag 18)(70 bytes)
Ver 1 Encrypted data (plain text + MDC SHA1(20 bytes))
PGPdump Interface, Copyright (c) 2001, Stefan H. Holek,
stefan(_at_)epy(_dot_)co(_dot_)at
is there any additional mdc information necessary/desirable to be displayed?
vedaal