Re: [OAUTH-WG] OAuth Bearer authentication - for proxies?

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Mon, 02 January 2012 22:17 UTC

Return-Path: <igor.faynberg@alcatel-lucent.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87A1921F8AB9 for <oauth@ietfa.amsl.com>; Mon, 2 Jan 2012 14:17:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 VCZRnarwLuvQ for <oauth@ietfa.amsl.com>; Mon, 2 Jan 2012 14:17:55 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id F065421F8AB8 for <oauth@ietf.org>; Mon, 2 Jan 2012 14:17:54 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q02MHpt2001865 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 2 Jan 2012 16:17:53 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q02MHoTx031983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 2 Jan 2012 16:17:51 -0600
Received: from [135.244.20.78] (faynberg.lra.lucent.com [135.244.20.78]) by umail.lucent.com (8.13.8/TPES) with ESMTP id q02MHbce020039; Mon, 2 Jan 2012 16:17:50 -0600 (CST)
Message-ID: <4F022CFA.80907@alcatel-lucent.com>
Date: Mon, 02 Jan 2012 17:17:30 -0500
From: Igor Faynberg <igor.faynberg@alcatel-lucent.com>
Organization: Alcatel-Lucent
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Amos Jeffries <squid3@treenet.co.nz>
References: <301AF9A4-395C-4B5A-8610-CD86BEE1401A@mnot.net> <abe2950b95b27818e9e6ebddc99a7b7e@treenet.co.nz> <4EFE7E22.9010200@treenet.co.nz> <4F014DF3.9030105@alcatel-lucent.com> <4F016837.3040904@treenet.co.nz> <4F018048.1020900@lodderstedt.net> <4F019E09.3070007@treenet.co.nz>
In-Reply-To: <4F019E09.3070007@treenet.co.nz>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: ietf-http-wg@w3.org, oauth@ietf.org
Subject: Re: [OAUTH-WG] OAuth Bearer authentication - for proxies?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: igor.faynberg@alcatel-lucent.com
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jan 2012 22:17:57 -0000

I am at a loss here; granted, it is a gray area...  Does it mean that 
RFC 2817 has not been implemented properly?

To make it simple: At the client, I establish a session key with the 
server, and then use it for confidentiality.  How is this key known to 
any proxy?

Igor

On 1/2/2012 7:07 AM, Amos Jeffries wrote:
> On 2/01/2012 11:00 p.m., Torsten Lodderstedt wrote:
> ...
>>
>> general note: I do not understand why caching proxies should impose a 
>> problem in case TLS is used (end2end). Could you please explain?
>
> Because TLS is hop-by-hop (in HTTP hops, end-to-end only in TCP hops). 
> Proxies which decrypt TLS and provide responses out of cache are 
> already deployed in many places. Mostly in the form of 
> reverse-proxies, but corporate decryption proxies are also on the 
> increase.
>
> AYJ