IETF Logo Mail Archive

Re: [hybi] WebSocket, TLS and intermediaries

Roberto Peon <fenix@google.com> Wed, 21 July 2010 00:11 UTC

Return-Path: <fenix@google.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 422FA3A65A5 for <hybi@core3.amsl.com>; Tue, 20 Jul 2010 17:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.976
X-Spam-Level:
X-Spam-Status: No, score=-105.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 uc0hJeW6jtpc for <hybi@core3.amsl.com>; Tue, 20 Jul 2010 17:11:04 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id DB63F3A6985 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:11:03 -0700 (PDT)
Received: from hpaq13.eem.corp.google.com (hpaq13.eem.corp.google.com [172.25.149.13]) by smtp-out.google.com with ESMTP id o6L0BJVe026391 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:11:19 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1279671079; bh=83k6kfj0zD7jGK2g24AgGDqc8kk=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=BsoPsGGYrm/65m6dsKANfkfaooQF69D+DQ2aOPg2ElFB60+M92Iy9co3n64tvO5QO UvcrJopjjZGaF3r2iucqw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=I5C1Qn6dl6zPnvDyXkUadt3PGprzTLoHDEq62tafhSGKw5po0Xxfh9SMQswKBYHX8 6Qgjs6qxxbmZ+kVhrGLvA==
Received: from vws9 (vws9.prod.google.com [10.241.21.137]) by hpaq13.eem.corp.google.com with ESMTP id o6L0BHnk032369 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:11:17 -0700
Received: by vws9 with SMTP id 9so6693409vws.38 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:11:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.115.157 with SMTP id i29mr6019165qaq.262.1279671076399; Tue, 20 Jul 2010 17:11:16 -0700 (PDT)
Received: by 10.229.106.214 with HTTP; Tue, 20 Jul 2010 17:11:16 -0700 (PDT)
In-Reply-To: <AANLkTikYNaK+JZL5OA1MOgTF4kHbimYQws_yUaSqpkaj@mail.gmail.com>
References: <h2w5c902b9e1004152345j992b815bz5f8d38f06a19181a@mail.gmail.com> <Pine.LNX.4.64.1004160701250.751@ps20323.dreamhostps.com> <4BC860FD.8080007@webtide.com> <Pine.LNX.4.64.1004161952530.751@ps20323.dreamhostps.com> <35EFEA5E-9017-48A1-BB66-A0AF947E159F@d2dx.com> <AANLkTinihlL2sn3Kiwtcl7QYKhFlvmj9lvmH4_z02xF7@mail.gmail.com> <FC1F510E-6D48-4D75-A356-F455C9FD5BD8@apple.com> <AANLkTikYNaK+JZL5OA1MOgTF4kHbimYQws_yUaSqpkaj@mail.gmail.com>
Date: Tue, 20 Jul 2010 17:11:16 -0700
Message-ID: <AANLkTimscmZpHaxFyV8Bcyzh6gBGAodcL1tw+29q5z+B@mail.gmail.com>
From: Roberto Peon <fenix@google.com>
To: John Tamplin <jat@google.com>
Content-Type: multipart/alternative; boundary="00c09f9b0bbaf02cf7048bdaa37c"
X-System-Of-Record: true
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] WebSocket, TLS and intermediaries
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: Wed, 21 Jul 2010 00:11:05 -0000

On Tue, Jul 20, 2010 at 5:04 PM, John Tamplin <jat@google.com> wrote:

> On Tue, Jul 20, 2010 at 8:01 PM, Maciej Stachowiak <mjs@apple.com> wrote:
>
>> This point is very important. Building on top of TLS has huge practical
>> benefits. I think this outweighs the desire to more easily build transparent
>> intermediaries. Any mechanism that allows intermediaries without being
>> authorized by either endpoint is by definition a security vulnerability in
>> the protocol.
>>
>> I think the benefits of TLS also outweigh the "amateur server implementor"
>> argument. I don't think we want to make it easy to implement a security
>> hole.
>>
>
> How would requiring TLS impact games over WebSocket, such as GWT Quake?
>  Maybe one day we will have a connection-oriented datagram protocol for WS,
> but until then we have to make do with running over TCP.  Adding encryption
> overhead might render WS unusable for this purpose.
>

I'd be pretty surprised if SSL added enough overhead that it made WS
unsuitable for games. It is far, far, far, more likely that the fact that
we're using TCP renders it useless for certain classes of games.

Also, while perhaps I don't count as an 'amateur' programmer, I did add
SSL/TLS support to a server recently. It tool no more than a day to do! t
was surprisingly easy!

-=R


> --
> John A. Tamplin
> Software Engineer (GWT), Google
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>
>

v2.23.0 | Report a Bug | By Email