Re: [hybi] Extensibility mechanisms?

Jamie Lokier <jamie@shareable.org> Mon, 26 July 2010 22:15 UTC

Return-Path: <jamie@shareable.org>
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 0CD233A6AB1 for <hybi@core3.amsl.com>; Mon, 26 Jul 2010 15:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.465
X-Spam-Level:
X-Spam-Status: No, score=-2.465 tagged_above=-999 required=5 tests=[AWL=0.134, BAYES_00=-2.599]
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 i8i718+4La1k for <hybi@core3.amsl.com>; Mon, 26 Jul 2010 15:15:49 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id CEA6A3A6A64 for <hybi@ietf.org>; Mon, 26 Jul 2010 15:15:48 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1OdVxu-0003zA-5N; Mon, 26 Jul 2010 23:16:06 +0100
Date: Mon, 26 Jul 2010 23:16:06 +0100
From: Jamie Lokier <jamie@shareable.org>
To: Adam Barth <ietf@adambarth.com>
Message-ID: <20100726221606.GC23142@shareable.org>
References: <Pine.LNX.4.64.1007212153110.7242@ps20323.dreamhostps.com> <AANLkTiku76oSucTNDFdwgsFBNFa_cCpC-YktTnMfX47-@mail.gmail.com> <4C479130.4020500@caucho.com> <AANLkTikLDjBP-Xs5t6TxmJuq4nG8jwThQ=n34B4cEmup@mail.gmail.com> <4C479CE4.6070805@caucho.com> <AANLkTims1er0Rbv0ysP4gRs1Kd0He8hapHeJ3nON=JQa@mail.gmail.com> <4C47C5B0.3030006@caucho.com> <AANLkTi=ND-FOH8OoD=TCbiyeSZ-h0LhxQBXN5w-2hfvj@mail.gmail.com> <4C48A468.3040009@caucho.com> <AANLkTikeLr325F03bowJu7NeHEqY_+OzEnQcrxHbCwhW@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AANLkTikeLr325F03bowJu7NeHEqY_+OzEnQcrxHbCwhW@mail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] Extensibility mechanisms?
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, 26 Jul 2010 22:15:50 -0000

Adam Barth wrote:
> On Thu, Jul 22, 2010 at 1:04 PM, Scott Ferguson <ferg@caucho.com> wrote:
> > The issue is the number of request/response before the initial payload is
> > sent. If we require the client to wait to validate the server before it can
> > send its payload, the initial performance will be slower than a HTTP POST.
> >
> > That delay may be perfectly acceptable, but some people have raised it as an
> > issue in the group. I'm fine with the delay myself, but I think it should be
> > resolved.
> 
> We need to know the server understands web sockets before spamming
> them with attacker-controlled bytes.  If we don't, we'll repeat the
> long and tragic history of cross-protocol vulnerabilities caused by
> HTTP POST.

Compliant implementations *already* spam the server with
attacker-controlled bytes in the initial handshake.

All proposals to include early payloads are explicitly designed to
tunnel it safely in a way which does no more harm than the initial
handshake.

I don't think I've seen any proposals for an insecure method or
sending arbitrary attacker-controlled bytes early, and I wonder if
you're making an incorrect assumption that.

-- Jamie