Re: [hybi] Upgrade Mechanism and HasMat (was Re: Extensibility mechanisms?)

Salvatore Loreto <salvatore.loreto@ericsson.com> Thu, 22 July 2010 10:24 UTC

Return-Path: <salvatore.loreto@ericsson.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 130213A67F0 for <hybi@core3.amsl.com>; Thu, 22 Jul 2010 03:24:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.25
X-Spam-Level:
X-Spam-Status: No, score=-4.25 tagged_above=-999 required=5 tests=[AWL=-1.651, 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 yoKyWQiQSLGU for <hybi@core3.amsl.com>; Thu, 22 Jul 2010 03:24:39 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 6A8103A6A8C for <hybi@ietf.org>; Thu, 22 Jul 2010 03:24:39 -0700 (PDT)
X-AuditID: c1b4fb39-b7b91ae000001aef-2c-4c481c773266
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id F2.87.06895.77C184C4; Thu, 22 Jul 2010 12:24:56 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 Jul 2010 12:24:55 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 Jul 2010 12:24:55 +0200
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 2BB1624DC; Thu, 22 Jul 2010 13:24:55 +0300 (EEST)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id EB9A84FBBD; Thu, 22 Jul 2010 13:24:54 +0300 (EEST)
Received: from n200.nomadiclab.com (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 9BD2A4F585; Thu, 22 Jul 2010 13:24:54 +0300 (EEST)
Message-ID: <4C481C76.1060907@ericsson.com>
Date: Thu, 22 Jul 2010 13:24:54 +0300
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: "Roy T. Fielding" <fielding@gbiv.com>
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> <20100722055452.GL7174@1wt.eu> <AANLkTik_rpxo=1OfzHkwpC5soQG_NxvGuZNXx7gdhVTh@mail.gmail.com> <20100722064945.GM7174@1wt.eu> <AANLkTim7AsQGSwLE51uktj=B1vB6roZChAtDoCrE6fFG@mail.gmail.com> <4C47FF71.3050000@ericsson.com> <18E0FF9C-6C51-4602-92E1-E44802D0D8B5@gbiv.com>
In-Reply-To: <18E0FF9C-6C51-4602-92E1-E44802D0D8B5@gbiv.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-OriginalArrivalTime: 22 Jul 2010 10:24:55.0640 (UTC) FILETIME=[21041D80:01CB2988]
X-Brightmail-Tracker: AAAAAA==
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Upgrade Mechanism and HasMat (was Re: 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: Thu, 22 Jul 2010 10:24:41 -0000

On 7/22/10 12:33 PM, Roy T. Fielding wrote:
> On Jul 22, 2010, at 1:21 AM, Salvatore Loreto wrote:
>
>    
>> I see more value to work on a general solution to secure the HTTP Upgrade mechanism
>> against cross-protocol vulnerability, instead of trying to draft something ad-hoc for WebSocket
>>      
> The HTTP Upgrade mechanism is not vulnerable to cross-protocol attacks.
> Other (non-HTTP) services are vulnerable to browser misdirection if
> the browser can be directed to send arbitrary bytes to an arbitrary
> TCP port.  That is a problem which HTTP is actually good at avoiding
> because the first line is unique to HTTP.
>    
Hi Roy,

thanks for the answer and to share your view.
as far I understood (but I have to admit not to be an expert on 
cross-protocol attacks),
the kind of attacks people are talking is restrict to HTTP - WebSocket 
(or viceversa) cross attack.

however if HTTP experts exclude any vulnerability in the HTTP Upgrade,
then a sort of security check right after the end of the Upgrade from 
HTTP to Websocket
and before the WebSocket starts to exchange data, could solve the problem.

> The issues people are raising about Upgrade are in regard to passing
> through intermediaries.  Some people believe that intermediaries are
> evil and must be tunneled through.  Other people believe that
> intermediaries are beneficial and any protocol that deliberately
> subverts them will be blocked.
>    
passing or not through intermediaries is a completely different protocol 
aspect the wg has make a decision on;
but I would prefer the decision be made clearly, not hidden behind 
security issues
especially if they do not exist !

cheers
/Sal
> There is no solution that will satisfy both of those beliefs.
> Please stop trying to reconcile irreconcilable belief systems.
>    
> Implement both.  One will succeed, the other will fail.
> Neither choice is mature enough for standardization at the
> current time.
>
> ....Roy
>
>
>    


-- 
Salvatore Loreto
www.sloreto.com