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

Scott Ferguson <ferg@caucho.com> Sat, 09 October 2010 15:59 UTC

Return-Path: <ferg@caucho.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 369133A68C7 for <hybi@core3.amsl.com>; Sat, 9 Oct 2010 08:59:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.209
X-Spam-Level:
X-Spam-Status: No, score=-2.209 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 9LI+Z5miyGQC for <hybi@core3.amsl.com>; Sat, 9 Oct 2010 08:59:25 -0700 (PDT)
Received: from smtp113.biz.mail.sp1.yahoo.com (smtp113.biz.mail.sp1.yahoo.com [69.147.92.226]) by core3.amsl.com (Postfix) with SMTP id 039133A68BE for <hybi@ietf.org>; Sat, 9 Oct 2010 08:59:24 -0700 (PDT)
Received: (qmail 18314 invoked from network); 9 Oct 2010 16:00:32 -0000
Received: from [192.168.1.11] (ferg@66.92.8.203 with plain) by smtp113.biz.mail.sp1.yahoo.com with SMTP; 09 Oct 2010 09:00:32 -0700 PDT
X-Yahoo-SMTP: L1_TBRiswBB5.MuzAo8Yf89wczFo0A2C
X-YMail-OSG: m3cJd9UVM1mAZzsnPMnkTBq_2EPCMG6DrR7ORu4TacorH2R vowsY4CN5LOhNExB8OcFjnPz3mwvycy5D3TyevHO85MFZFOzUBeGE0rndg46 x9CLSvxDy4WWMgdw7M640CrPJP.PLW2hg9OXJ8tiXmAEq3XxhnChwal2JZnl 7Zyw3Yj42VRUCJAYZa0m._2IIRtcfhKK4pKJyu259kYEZWLyCT_v55cacmD0 E0PcOQ22zbRWGD9Sjwjrne3Mde4elgH4GWGbg.SGIpV2xkzshpH4.rKBuwyd kjC569pHwAfDE.xb8O3rJ
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4CB0919F.8030603@caucho.com>
Date: Sat, 09 Oct 2010 09:00:31 -0700
From: Scott Ferguson <ferg@caucho.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Willy Tarreau <w@1wt.eu>
References: <AANLkTi=nLixtxMEd4B58Zp5FRbquNX2C_=7gCf9BGGQs@mail.gmail.com> <4CABCBFA.6020100@caucho.com> <AANLkTi=5wbCXWpOtUQT1MndgCxt9gj6uR_3U=nONpjKc@mail.gmail.com> <4CABD11F.3060500@caucho.com> <AANLkTiksehiSp7DB17MBVBb457p6pN5E8vma6FHz1c9j@mail.gmail.com> <4CACA667.3040309@caucho.com> <4CAF9589.1060007@caucho.com> <AANLkTinnnT5Oib7FvDdZF2q_WUT8=q8KNmfkfajE0Mor@mail.gmail.com> <4CAFA043.10101@caucho.com> <AANLkTi=eo-cjBz160FN0cn53v4-CpDSYaEneqkr_ZP7k@mail.gmail.com> <20101009055412.GK4712@1wt.eu>
In-Reply-To: <20101009055412.GK4712@1wt.eu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Sat, 09 Oct 2010 15:59:26 -0000

Willy Tarreau wrote:
> No Adam. All what you're trying to do is to protect against a socket data
> being taken as a new request. As I already said it several times now, we
> just have to set "Connection: close" in the request to put an end on that.
> We definitely don't want to risk that confusion !
>
> >From draft-ietf-httpbis-p1-messaging-11 :
>    7.1.2.1. Negotiation
>    An HTTP/1.1 server MAY assume that a HTTP/1.1 client intends to
>    maintain a persistent connection unless a Connection header including
>    the connection-token "close" was sent in the request.
>    ...
>    If either the client or the server sends the close token in the
>    Connection header, that request becomes the last one for the
>    connection.
>
> As you see, this is by definition, so we must use the close header and
> we need to focus on real cross-protocol attacks, not the ones between
> WS and HTTP servers based on the second request.
>   

+1

-- Scott