IETF Logo Mail Archive

Re: [hybi] WebSocket, TLS and intermediaries

John Tamplin <jat@google.com> Wed, 21 July 2010 00:04 UTC

Return-Path: <jat@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 915CC3A65A5 for <hybi@core3.amsl.com>; Tue, 20 Jul 2010 17:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.976
X-Spam-Level:
X-Spam-Status: No, score=-101.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 ZeJrksufEsaH for <hybi@core3.amsl.com>; Tue, 20 Jul 2010 17:04:53 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 7CB973A6970 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:04:53 -0700 (PDT)
Received: from hpaq3.eem.corp.google.com (hpaq3.eem.corp.google.com [172.25.149.3]) by smtp-out.google.com with ESMTP id o6L058G1023720 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:05:08 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1279670708; bh=QzNCF9/wFFXwi6JEWqgG2SsLdEM=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=aUe5Z05X0j2v7qvCeGzeVCPTdvHRObYpAdwUUnls/dPq/RrrXqmeIzGBPrKSCqbEm HjoZgq4mHbbEvS1KQ23Nw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=vcWJ7rALqhQ+lj/YXl4rHA9Wu4FInUBI/sz9iS1Arn2VMgZr5MnRhC7ZgutjcP4Qh 0fmWN24DEaKn/+JKFc7Vg==
Received: from qyk7 (qyk7.prod.google.com [10.241.83.135]) by hpaq3.eem.corp.google.com with ESMTP id o6L052rK010285 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:05:07 -0700
Received: by qyk7 with SMTP id 7so2456559qyk.4 for <hybi@ietf.org>; Tue, 20 Jul 2010 17:05:07 -0700 (PDT)
Received: by 10.224.113.85 with SMTP id z21mr6031468qap.214.1279670707196; Tue, 20 Jul 2010 17:05:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.78.193 with HTTP; Tue, 20 Jul 2010 17:04:46 -0700 (PDT)
In-Reply-To: <FC1F510E-6D48-4D75-A356-F455C9FD5BD8@apple.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>
From: John Tamplin <jat@google.com>
Date: Tue, 20 Jul 2010 20:04:46 -0400
Message-ID: <AANLkTikYNaK+JZL5OA1MOgTF4kHbimYQws_yUaSqpkaj@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Content-Type: multipart/alternative; boundary="000feaead823ee9961048bda8d50"
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:04:54 -0000

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.

-- 
John A. Tamplin
Software Engineer (GWT), Google

v2.23.0 | Report a Bug | By Email