RE: [TLS] Serious crypto problem fixed by envelope HMAC methodinstead of currently used prefix
"Blumenthal, Uri" <uri.blumenthal@intel.com> Mon, 27 November 2006 19:31 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GomCH-000223-75; Mon, 27 Nov 2006 14:31:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GomCG-00021s-Hf for TLS@lists.ietf.org; Mon, 27 Nov 2006 14:31:20 -0500
Received: from mga01.intel.com ([192.55.52.88]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GomCF-0007bX-7s for TLS@lists.ietf.org; Mon, 27 Nov 2006 14:31:20 -0500
Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by mga01.intel.com with ESMTP; 27 Nov 2006 11:31:07 -0800
Received: from fmsmsx334.amr.corp.intel.com ([132.233.42.1]) by fmsmga001.fm.intel.com with ESMTP; 27 Nov 2006 11:31:06 -0800
X-ExtLoop1: 1
X-IronPort-AV: i="4.09,464,1157353200"; d="scan'208"; a="169601940:sNHT34671616"
Received: from hdsmsx412.amr.corp.intel.com ([10.127.2.72]) by fmsmsx334.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 27 Nov 2006 11:31:06 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [TLS] Serious crypto problem fixed by envelope HMAC methodinstead of currently used prefix
Date: Mon, 27 Nov 2006 14:31:04 -0500
Message-ID: <279DDDAFA85EC74C9300A0598E704056FE74AC@hdsmsx412.amr.corp.intel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [TLS] Serious crypto problem fixed by envelope HMAC methodinstead of currently used prefix
thread-index: AccSWb3bTW/M59oURD+M+/FTlCLt6QAAG2UA
From: "Blumenthal, Uri" <uri.blumenthal@intel.com>
To: TLS@lists.ietf.org
X-OriginalArrivalTime: 27 Nov 2006 19:31:06.0613 (UTC) FILETIME=[95650250:01C7125A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc:
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org
>> SSLv3 used a variant of the original HMAC (pre-2104). >> IIRC, SSLv2 didn't use HMAC and *did* have an extension >> attack, but that's hardly our problem at this point. > > But does SSL v2 has the lenth field protection > (as we discussed) against an extension attack? > Can somebody send me the function used in SSL v2? As SSLv2 is a technically-dead protocol (that is not thrown out from the code only for compatibility reasons), how relevant is it now??? _______________________________________________ TLS mailing list TLS@lists.ietf.org https://www1.ietf.org/mailman/listinfo/tls
- RE: [TLS] Serious crypto problem fixed by envelop… Peter Williams
- RE: [TLS] Serious crypto problem fixed by envelop… Jan Mikkelsen
- RE: [TLS] Serious crypto problem fixed by envelop… Blumenthal, Uri
- Re: [TLS] Serious crypto problem fixed by envelop… Steven M. Bellovin