IETF Logo Mail Archive

Re: separation of signed and encrypted messages

"vedaal" <vedaal@hotmail.com> Tue, 16 October 2001 17:22 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11490 for <openpgp-archive@odin.ietf.org>; Tue, 16 Oct 2001 13:22:53 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id f9GH92S05238 for ietf-openpgp-bks; Tue, 16 Oct 2001 10:09:02 -0700 (PDT)
Received: from hotmail.com (oe55.law3.hotmail.com [209.185.240.55]) by above.proper.com (8.11.6/8.11.3) with ESMTP id f9GH90D05234 for <ietf-openpgp@imc.org>; Tue, 16 Oct 2001 10:09:00 -0700 (PDT)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 16 Oct 2001 10:08:57 -0700
X-Originating-IP: [63.211.85.132]
From: vedaal <vedaal@hotmail.com>
To: ietf-openpgp@imc.org, Michael Young <mwy-opgp97@the-youngs.org>
References: <OE58s955E3yIyEOadke00001939@hotmail.com> <008201c15657$4b6f1880$dfc32609@transarc.ibm.com>
Subject: Re: separation of signed and encrypted messages
Date: Tue, 16 Oct 2001 13:08:23 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <OE55rFHLqbp3eccmgeR00001add@hotmail.com>
X-OriginalArrivalTime: 16 Oct 2001 17:08:57.0913 (UTC) FILETIME=[3E3FAA90:01C15665]
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

- ----- Original Message ----- 
From: "Michael Young" <mwy-opgp97@the-youngs.org>
To: <ietf-openpgp@imc.org>
Sent: Tuesday, October 16, 2001 11:29 AM
Subject: Re: separation of signed and encrypted messages


 
> If you're willing to show the plaintext, why do you care about
> protecting the session key?  Are you reusing it?  This might be an
> issue for a PGPdisk, for example, where one symmetric key protects the
> entire contents...  you can't reveal+prove selected parts.  

for an rsa key,
if one has the session key, ciphertext and plaintext,
and, at some point, 
*if*
md5 is 'fully' broken,
would it not be possible to retrieve the secret key and passphrase?


vedaal

-----BEGIN PGP SIGNATURE-----
Version: 6.5.8ckt http://www.ipgpp.com/
Comment: { Acts of Kindness better the World, and protect the Soul }
Comment: KeyID: 0x6A05A0B785306D25
Comment: Fingerprint: 96A6 5F71 1C43 8423  D9AE 02FD A711 97BA

iQEVAwUBO8xphmoFoLeFMG0lAQOeXgf+L0PAnxSnZ6NXzM9wfJN+4IquwhjMsJXQ
Y3Odn6TDcPTJY9CA8IHYNCoh59b0pAwwR4R9phmRaIbH45HmmKLTZBXei8UtI3Ok
J162JyJTcas8SMKkMNJTz5q1GJ3V+Ij8TevJAAWjYH1CL1zoZ/xIYfLauLP4HocB
rFhrQm/QvYYse+qbCEm+erkY5SlarmkG4w/GjRWQPkjASNzNX6xZBsywKuqTUcYi
+pI2el+JUSvVD9VHTHlMb7xE0Awfmp3c5v7OCKTrz6uaON7BN52MXRJlXZK8VAvT
5ee6wwyn5FoatHAjnf/Z/GAvcJQdLj8rYTF719BF4wLoi1wX0frNKA==
=FR1H
-----END PGP SIGNATURE-----

v2.23.0 | Report a Bug | By Email