IETF Logo Mail Archive

Re: [TLS] AES and SSLv3 (was Re: Unfortunate current practices for HTTP

Wan-Teh Chang <wtc@google.com> Wed, 19 January 2011 01:52 UTC

Return-Path: <wtc@google.com>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49A173A6FE1 for <tls@core3.amsl.com>; Tue, 18 Jan 2011 17:52:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5+QBdEGHpb2 for <tls@core3.amsl.com>; Tue, 18 Jan 2011 17:52:12 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 4A41B3A6F34 for <tls@ietf.org>; Tue, 18 Jan 2011 17:52:12 -0800 (PST)
Received: from wpaz17.hot.corp.google.com (wpaz17.hot.corp.google.com [172.24.198.81]) by smtp-out.google.com with ESMTP id p0J1sosx014360 for <tls@ietf.org>; Tue, 18 Jan 2011 17:54:50 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1295402090; bh=vtIeQmz1oGdleqQyTbDKgGfv9yw=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=Sll4tP81m8FI0NrCBENCm3/vEgMZbZiXb1QjmpB15VKM+G/Pbk2DFAyEI2EzhPNj/ LYTaUiAJaYWZsHHznWUhg==
Received: from wwb39 (wwb39.prod.google.com [10.241.241.103]) by wpaz17.hot.corp.google.com with ESMTP id p0J1smQa010874 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <tls@ietf.org>; Tue, 18 Jan 2011 17:54:49 -0800
Received: by wwb39 with SMTP id 39so339326wwb.4 for <tls@ietf.org>; Tue, 18 Jan 2011 17:54:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mDpa7Efg4jWzdRzZWtdKcJdeOOHlwGSlfNAfDzu+cTY=; b=mmWs64xc8g0GuSVvgCzxNIawTi6sG6aCXtn9lZA6tacRVXa0voxbDalSlnIcKw2cjc A5HycFlIKoZmROIVLo7w==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=wRk9T6TtGKk2oobme3tkjF0RlcwPinm1XO1G4lnhiV/rJplilqOskR5StTLEqjgw6H jSXjuh+5LUyrMxUE56hw==
MIME-Version: 1.0
Received: by 10.216.176.142 with SMTP id b14mr69897wem.32.1295402039583; Tue, 18 Jan 2011 17:53:59 -0800 (PST)
Received: by 10.216.6.81 with HTTP; Tue, 18 Jan 2011 17:53:59 -0800 (PST)
In-Reply-To: <201101190113.p0J1DLPw018889@fs4113.wdf.sap.corp>
References: <4D363198.2050301@pobox.com> <201101190113.p0J1DLPw018889@fs4113.wdf.sap.corp>
Date: Tue, 18 Jan 2011 17:53:59 -0800
Message-ID: <AANLkTikqOpvsfF06u2V4NLF6ncDGsJ39brFNEViOSxYG@mail.gmail.com>
From: Wan-Teh Chang <wtc@google.com>
To: mrex@sap.com
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: tls@ietf.org
Subject: Re: [TLS] AES and SSLv3 (was Re: Unfortunate current practices for HTTP
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2011 01:52:13 -0000

On Tue, Jan 18, 2011 at 5:13 PM, Martin Rex <mrex@sap.com> wrote:
>
> But I know of at least one TLS implementation shipped by a large vendor
> that aborts on the combination of rfc-3268 cipher suites and SSLv3.

Eric Lawrence explained this in the blog post "AES is not a valid
cipher for SSLv3":
http://blogs.msdn.com/b/ieinternals/archive/2009/12/08/aes-is-not-a-valid-cipher-for-sslv3.aspx

Wan-Teh

v2.23.0 | Report a Bug | By Email