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

Igor Faynberg <igor.faynberg@alcatel-lucent.com> Mon, 02 January 2012 06:26 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 10D3821F8F06 for <oauth@ietfa.amsl.com>; Sun, 1 Jan 2012 22:26:12 -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 JHfIhjJq-8O6 for <oauth@ietfa.amsl.com>; Sun, 1 Jan 2012 22:26:11 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 73C6221F8D3E for <oauth@ietf.org>; Sun, 1 Jan 2012 22:26:11 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q026Q6ut011990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 2 Jan 2012 00:26:09 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q026Q6S6006237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 2 Jan 2012 00:26:06 -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 q026Pu0U004085; Mon, 2 Jan 2012 00:26:04 -0600 (CST)
Message-ID: <4F014DF3.9030105@alcatel-lucent.com>
Date: Mon, 02 Jan 2012 01:25:55 -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>
In-Reply-To: <4EFE7E22.9010200@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.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
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 06:26:12 -0000

On 12/30/2011 10:14 PM, Amos Jeffries wrote:
> ....
>>
>> Reading section 2.3, it appears this method of transferring the 
>> credentials is open to replay attacks when caching TLS middleware is 
>> present. I believe this spec should mandate cache controls on 
>> responses using that method. Otherwise a lot of HTTP compliant 
>> middleware will feel free to store and supply the protected response 
>> to later replay attacks.
>>
>
Amos,

I believe that the draft addresses the replay matters by  specifying the 
validity time field. Do you see a problem with that?

(I did not understand what "HTTP-compliant middleware" meant, but if it 
is something at the proxies, I think this is further addressed by making 
TLS a must--which will make the token simply invisible.)

With best wishes for the New Year to you and all OAuthers,

Igor

Igor