Re: [hybi] A bit of pragmatism

Bruce Atherton <bruce@callenish.com> Sun, 09 January 2011 22:00 UTC

Return-Path: <bruce@callenish.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 E5E2A3A6850 for <hybi@core3.amsl.com>; Sun, 9 Jan 2011 14:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level:
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 QbH1742ojK+E for <hybi@core3.amsl.com>; Sun, 9 Jan 2011 14:00:26 -0800 (PST)
Received: from biz82.inmotionhosting.com (biz82.inmotionhosting.com [74.124.202.87]) by core3.amsl.com (Postfix) with ESMTP id 960D73A67D4 for <hybi@ietf.org>; Sun, 9 Jan 2011 14:00:26 -0800 (PST)
Received: from [24.108.133.142] (helo=[192.168.145.101]) by biz82.inmotionhosting.com with esmtpa (Exim 4.69) (envelope-from <bruce@callenish.com>) id 1Pc3LR-0006dK-D1 for hybi@ietf.org; Sun, 09 Jan 2011 14:02:37 -0800
Message-ID: <4D2A307C.3080109@callenish.com>
Date: Sun, 09 Jan 2011 14:02:36 -0800
From: Bruce Atherton <bruce@callenish.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: hybi@ietf.org
References: <20110106221426.GA28367@1wt.eu> <AANLkTimNc6YDUG=920P=G7kxs9oDwDEsGJ5LA6BG_iyb@mail.gmail.com> <20110107053410.GG28367@1wt.eu> <AANLkTinQADv+iq50=dsvK13cu1YdS5sb+xHvDZnfdOjB@mail.gmail.com> <20110107061043.GJ28367@1wt.eu> <AANLkTikHXQza-gx=tqD7jZ+ueQZTXa9acRVG+bBfdApG@mail.gmail.com> <20110107063854.GN28367@1wt.eu> <670C37A1-B413-49C0-8C47-E2E06DB447ED@apple.com> <20110107185801.GB32612@1wt.eu> <AANLkTinLf4z9S0EatVRi5ZdeEPcuJrOmvn6cpAELtf2w@mail.gmail.com> <20110107203958.GC32612@1wt.eu> <AANLkTinWX4k2mbGqK5qbiVtCTATC38xKJApLHCEuce85@mail.gmail.com> <4D28DF6E.4080003@callenish.com> <AANLkTikhgk7yRoC1K37QetW-7ZHw8G26WZVUs7fM2y=J@mail.gmail.com>
In-Reply-To: <AANLkTikhgk7yRoC1K37QetW-7ZHw8G26WZVUs7fM2y=J@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz82.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - callenish.com
Subject: Re: [hybi] A bit of pragmatism
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: Sun, 09 Jan 2011 22:00:28 -0000

Thanks for the correction, but I still don't understand.

If you are suggesting your mask for the wss: scheme in order to provide 
for a stream of apparent random bits on the wire, then that makes 
perfect sense. But for the purposely less-secure unencrypted ws: scheme 
I don't understand why it would be necessary.

On 08/01/2011 4:00 PM, Eric Rescorla wrote:
> On Sat, Jan 8, 2011 at 2:04 PM, Bruce Atherton<bruce@callenish.com>  wrote:
>> On 07/01/2011 1:19 PM, Eric Rescorla wrote:
>>> My objective is to make the bits that appear on the wire indistinguishable
>>> from random
>>> from the attacker's perspective. I think it's clear that this is the
>>> strongest form of masking
>>> available, and the method I proposed does that.
>> It is true that your goal is clear, but I don't understand why you think
>> this goal is necessary.
>>
>> The specification already allows for two forms of Websocket, a simple one
>> denoted by the scheme "ws:" and a secure one denoted with "wss:". The latter
>> one will have the random byte stream characteristics you are interested in.
>> If you are uncomfortable with any other kind of stream, make sure your
>> client only supports secure Websockets.
> Regrettably, this is not the case except for certain specific ciphers
> (in particular
> block cipher in CBC mode.) It's not at all the case for RC4 and only
> the case for
> some CTR mode implementations.
>
> Best,
> -Ekr