Re: [hybi] Handshake was: The WebSocket protocol issues.

Adam Barth <ietf@adambarth.com> Mon, 11 October 2010 16:58 UTC

Return-Path: <ietf@adambarth.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F2E63A6B4C for <hybi@core3.amsl.com>; Mon, 11 Oct 2010 09:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.984
X-Spam-Level:
X-Spam-Status: No, score=-1.984 tagged_above=-999 required=5 tests=[AWL=-0.007, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 PnDQLfysgtNB for <hybi@core3.amsl.com>; Mon, 11 Oct 2010 09:58:40 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 404323A6B1F for <hybi@ietf.org>; Mon, 11 Oct 2010 09:58:40 -0700 (PDT)
Received: by vws12 with SMTP id 12so813896vws.31 for <hybi@ietf.org>; Mon, 11 Oct 2010 09:59:52 -0700 (PDT)
Received: by 10.220.203.201 with SMTP id fj9mr1761325vcb.60.1286816392178; Mon, 11 Oct 2010 09:59:52 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id z36sm1882179vbw.7.2010.10.11.09.59.49 (version=SSLv3 cipher=RC4-MD5); Mon, 11 Oct 2010 09:59:49 -0700 (PDT)
Received: by iwn10 with SMTP id 10so4903257iwn.31 for <hybi@ietf.org>; Mon, 11 Oct 2010 09:59:48 -0700 (PDT)
Received: by 10.231.182.204 with SMTP id cd12mr4838021ibb.101.1286816388261; Mon, 11 Oct 2010 09:59:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.72.205 with HTTP; Mon, 11 Oct 2010 09:59:17 -0700 (PDT)
In-Reply-To: <0se6b6h4uf1akqbsrn700ns56nl7kevbkf@hive.bjoern.hoehrmann.de>
References: <AANLkTinv5Ym5jwUEqS76z3UkVa7GpmOBT_WXhBbFK0-m@mail.gmail.com> <20101009055723.GL4712@1wt.eu> <AANLkTimY2DjxgZybibSRtc7L34Wns2KhQC=Wa9K6PYku@mail.gmail.com> <20101009204009.GP4712@1wt.eu> <AANLkTi=Az0RmE1Uipo068zMh3YzgMpM2tQ+zYxaDT47A@mail.gmail.com> <20101011053354.GA12672@1wt.eu> <4CB2D7BD.1070004@opera.com> <9B9FA451-5551-4434-8EC1-BAC834FB9A61@apple.com> <AANLkTimDc_aqRTtgRpMKhdhk6x+vPGyOPvU3A=6mK9S7@mail.gmail.com> <4CB3373C.5050507@opera.com> <0se6b6h4uf1akqbsrn700ns56nl7kevbkf@hive.bjoern.hoehrmann.de>
From: Adam Barth <ietf@adambarth.com>
Date: Mon, 11 Oct 2010 09:59:17 -0700
Message-ID: <AANLkTikwbOb01Q6x8giLv1TfBqEDphD2rLObHzjyTAfF@mail.gmail.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: hybi <hybi@ietf.org>
Subject: Re: [hybi] Handshake was: The WebSocket protocol issues.
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 16:58:41 -0000

On Mon, Oct 11, 2010 at 9:49 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> * James Graham wrote:
>>So there is an underlying issue here that I don't understand. It seems
>>clear to me that Adam and Eric's proposed handshake has a better
>>security story with regard to cross-protocol attacks than -75, -76, or
>>any other proposal other than using NPN with TLS. However there seem to
>>be a number of people who have problems with this proposed handshake to
>>the extent that they are prepared to forgo the security properties in
>>order to get something different. In general people seem to be aware
>>that they are making the security weaker since the arguments are mostly
>>about how different approaches will probably be good enough in practice
>>even though they are theoretically inferior.
>>
>>What I haven't followed is what the problems with the proposal actually
>>are. I understand that I have likely missed these in other messages, but
>>it would be helpful if people who believe that the proposed approach, or
>>aspects of it, are unworkable could summarise the outstanding issues
>>they see.
>
> The conceptional difference between the CONNECT proposal and the Upgrade
> proposal is that the former does not re-use the normal HTTP routing in-
> formation (path, host, port) meaning you may have to implement Websocket
> at a higher level than you might want to. There seems to be a lack of
> data if using CONNECT is problematic and/or beneficial. The only other
> part of the proposal is essentially "all traffic should be randomized",
> and that has been proposed for either approach.

The use of encryption and the use of CONNECT are indeed separable.

Adam