Re: [OAUTH-WG] SWT for indicating sites where a token is valid

Marius Scurtescu <mscurtescu@google.com> Mon, 10 May 2010 23:51 UTC

Return-Path: <mscurtescu@google.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78BE03A6AA9 for <oauth@core3.amsl.com>; Mon, 10 May 2010 16:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.324
X-Spam-Level:
X-Spam-Status: No, score=-100.324 tagged_above=-999 required=5 tests=[AWL=-0.761, BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, 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 0lsqrbyXl0aV for <oauth@core3.amsl.com>; Mon, 10 May 2010 16:51:39 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 7B0DC3A67AD for <oauth@ietf.org>; Mon, 10 May 2010 16:51:39 -0700 (PDT)
Received: from kpbe11.cbf.corp.google.com (kpbe11.cbf.corp.google.com [172.25.105.75]) by smtp-out.google.com with ESMTP id o4ANpHqO024631 for <oauth@ietf.org>; Mon, 10 May 2010 16:51:18 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1273535478; bh=IHLVf402zZw9Qq5okH+qvn2jQdQ=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=p5bs20nPNIIj5qfs2KxmG7HR7+sFFvpxOaCgVPI+8kDPqPSjRa0BGbzyXqZ/qYgb/ WZ17UUMlWy0pEx33bqsRw==
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=Z/c1W2OipY2A4EaDISQXSp3svSFMazpFZIMBmmeyoXt1+w71okLzS4gexNvN6/Sj4 tWLGSnMjfFTmwM4gVULlw==
Received: from pwi9 (pwi9.prod.google.com [10.241.219.9]) by kpbe11.cbf.corp.google.com with ESMTP id o4ANpGh2021034 for <oauth@ietf.org>; Mon, 10 May 2010 16:51:16 -0700
Received: by pwi9 with SMTP id 9so2065032pwi.13 for <oauth@ietf.org>; Mon, 10 May 2010 16:51:16 -0700 (PDT)
Received: by 10.141.107.19 with SMTP id j19mr3194734rvm.90.1273535476085; Mon, 10 May 2010 16:51:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.141.125.21 with HTTP; Mon, 10 May 2010 16:50:56 -0700 (PDT)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1126328511A@WSMSG3153V.srv.dir.telstra.com>
References: <255B9BB34FB7D647A506DC292726F6E11263073D6D@WSMSG3153V.srv.dir.telstra.com> <q2hfd6741651005062105y46152452x370fac0dd12d55c6@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E112631B24FC@WSMSG3153V.srv.dir.telstra.com> <4BE3A5DC.5030601@lodderstedt.net> <BC9EED4C-B667-4AC2-A663-CEAC0B7CB620@lodderstedt.net> <AANLkTincZ8_0-t2r_Ey9BestA_knMciYsxRLyHcOvSVO@mail.gmail.com> <g2xfd6741651005071106if93ba794q7e9739669eb22fc2@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E112631B2989@WSMSG3153V.srv.dir.telstra.com> <AANLkTinUEWwq2pxLukMrwDHeth-86THV_uvGWCrFjskU@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1126328511A@WSMSG3153V.srv.dir.telstra.com>
From: Marius Scurtescu <mscurtescu@google.com>
Date: Mon, 10 May 2010 16:50:56 -0700
Message-ID: <AANLkTimgXfVZc5-51FPsamrQPhj8EyXIeAa5qpQFhe3S@mail.gmail.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] SWT for indicating sites where a token is valid
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 10 May 2010 23:51:40 -0000

On Mon, May 10, 2010 at 4:46 PM, Manger, James H
<James.H.Manger@team.telstra.com> wrote:
> Marius,
>
>> As a side note, I was thinking more about the suggested "sites"
>> parameter. In practice that sites where an access token can be used is
>> limited to what protected resources can decrypt or verify the token.
>> An access token cannot be really used at the wrong site. A "sites"
>> parameter could be a nice hint for the client, but not a security
>> requirement.
>
>
> A bearer token that goes to the wrong site can be used -- to access the protected resource on the right site -- so this is a total security failure, not a nice hint.

Yes, you are right. I was thinking about information leak from the
token. But then again, how does the client end up making a request to
the wrong site?


> If the wrong site uses HTTP then the token is also exposed on the network -- so it has just been broadcast in the clear if you are using public wifi. Again a security failure.

Sure, but the "sites" parameter does not help in these cases.


Marius