Re: [hybi] I-D Action: draft-ietf-hybi-thewebsocketprotocol-13.txt

Sylvain Hellegouarch <sh@defuze.org> Wed, 07 September 2011 07:34 UTC

Return-Path: <sh@defuze.org>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0287021F8C1E for <hybi@ietfa.amsl.com>; Wed, 7 Sep 2011 00:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.926
X-Spam-Level:
X-Spam-Status: No, score=-2.926 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mndsmn4L3mLn for <hybi@ietfa.amsl.com>; Wed, 7 Sep 2011 00:34:15 -0700 (PDT)
Received: from mail-gx0-f170.google.com (mail-gx0-f170.google.com [209.85.161.170]) by ietfa.amsl.com (Postfix) with ESMTP id 39ADD21F8C1D for <hybi@ietf.org>; Wed, 7 Sep 2011 00:34:15 -0700 (PDT)
Received: by gxk27 with SMTP id 27so4493276gxk.15 for <hybi@ietf.org>; Wed, 07 Sep 2011 00:36:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.16.134 with SMTP id g6mr11589217pbd.351.1315380962066; Wed, 07 Sep 2011 00:36:02 -0700 (PDT)
Received: by 10.142.113.8 with HTTP; Wed, 7 Sep 2011 00:36:02 -0700 (PDT)
X-Originating-IP: [195.101.247.164]
In-Reply-To: <20110907073055.GD16712@1wt.eu>
References: <20110831184207.1514.64093.idtracker@ietfa.amsl.com> <0fc901cc6878$1681eec0$0a00a8c0@Venus> <CAH9hSJb2rH+fX0AnekYxsEkHKzb15aHrg_hDQw1baWLiWBF-3w@mail.gmail.com> <CALkdAkjMro781JiQE7R8wZQf6zW83d25YWiy=QBEgdyJTHXepA@mail.gmail.com> <20110907073055.GD16712@1wt.eu>
Date: Wed, 07 Sep 2011 09:36:02 +0200
Message-ID: <CALkdAkhuwYdPYQ+eLhQkuJ3HHPUsaXN+zDnL9rA6Mi45NYFQKQ@mail.gmail.com>
From: Sylvain Hellegouarch <sh@defuze.org>
To: Willy Tarreau <w@1wt.eu>
Content-Type: multipart/alternative; boundary="bcaec52155affd023904ac54fe7c"
Cc: hybi@ietf.org
Subject: Re: [hybi] I-D Action: draft-ietf-hybi-thewebsocketprotocol-13.txt
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Wed, 07 Sep 2011 07:34:16 -0000

On Wed, Sep 7, 2011 at 9:30 AM, Willy Tarreau <w@1wt.eu> wrote:

> On Wed, Sep 07, 2011 at 09:14:52AM +0200, Sylvain Hellegouarch wrote:
> > Since the masking and unmasking are the same operations, I fail to
> > understand the added complexity of server-to-client masking. Clients
> already
> > know how to unmask since they can mask in the first place with the same
> > operation.
>
> Except they don't know the masking key. The purpose of masking is not
> to prevent a *client* from emitting the data it wants, but to prevent
> some *javascript code* running in a browser from doing so. The client
> is not the issue here, the issue is the fact that the attacker on the
> server side might easily make a client execute some controlled JS code.
> We want to ensure that someone who's present at both ends cannot easily
> control the byte stream sent by the client. And since the JS does not
> know the key, there's no easy way to perform the operation backwards
> first.
>
>
I suggest section 5.1 to be clarified with that point then.

-- 
- Sylvain
http://www.defuze.org
http://twitter.com/lawouach