Re: [TLS] New draft for "next protocol"
Florian Weimer <fweimer@bfk.de> Tue, 31 May 2011 07:03 UTC
Return-Path: <fweimer@bfk.de>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20FA1E0798 for <tls@ietfa.amsl.com>; Tue, 31 May 2011 00:03:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78xqeCKO934z for <tls@ietfa.amsl.com>; Tue, 31 May 2011 00:03:55 -0700 (PDT)
Received: from mx01.bfk.de (mx01.bfk.de [193.227.124.2]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA89E068B for <tls@ietf.org>; Tue, 31 May 2011 00:03:55 -0700 (PDT)
Received: from mx00.int.bfk.de ([10.119.110.2]) by mx01.bfk.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1QRIzO-0003sX-EV; Tue, 31 May 2011 07:03:48 +0000
Received: by bfk.de with local id 1QRIz2-0005r8-Tf; Tue, 31 May 2011 07:03:20 +0000
From: Florian Weimer <fweimer@bfk.de>
To: Adam Langley <agl@google.com>
References: <24ADE5FF-FDEE-493E-A00A-F6C5F274A7C3@vpnc.org> <4851D6E10A7F63448F4B32C3E2814AC91772C79D@SEAEMBX02.olympus.F5Net.com> <BANLkTi=4H0kOK-tw79FR5yEzVhuhwZy6eA@mail.gmail.com>
Date: Tue, 31 May 2011 07:03:20 +0000
In-Reply-To: <BANLkTi=4H0kOK-tw79FR5yEzVhuhwZy6eA@mail.gmail.com> (Adam Langley's message of "Wed, 18 May 2011 13:06:35 -0700")
Message-ID: <82tycbs66f.fsf@mid.bfk.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] New draft for "next protocol"
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.12
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/options/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: Tue, 31 May 2011 07:03:56 -0000
* Adam Langley: > Previous versions of the websockets protocol have had to be > reverted[1] because of cross-protocol attacks where an attacker > creates confusion about which protocol is being used. Are you sure that analysis was correct? I'm reasonably certain that it's not. In other words, you got punked. -- Florian Weimer <fweimer@bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- [TLS] New draft for "next protocol" Paul Hoffman
- Re: [TLS] New draft for "next protocol" David Holmes
- Re: [TLS] New draft for "next protocol" Adam Langley
- Re: [TLS] New draft for "next protocol" Matt McCutchen
- Re: [TLS] New draft for "next protocol" Adam Langley
- Re: [TLS] New draft for "next protocol" Florian Weimer