IETF Logo Mail Archive

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

"Manger, James H" <James.H.Manger@team.telstra.com> Tue, 11 May 2010 00:36 UTC

Return-Path: <James.H.Manger@team.telstra.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 5B5B228C0F9 for <oauth@core3.amsl.com>; Mon, 10 May 2010 17:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.416
X-Spam-Level: *
X-Spam-Status: No, score=1.416 tagged_above=-999 required=5 tests=[AWL=-0.283, BAYES_50=0.001, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
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 i5YNvzISeU-V for <oauth@core3.amsl.com>; Mon, 10 May 2010 17:36:53 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by core3.amsl.com (Postfix) with ESMTP id 645753A67AD for <oauth@ietf.org>; Mon, 10 May 2010 17:36:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,203,1272808800"; d="scan'208";a="3013389"
Received: from unknown (HELO ipcbni.tcif.telstra.com.au) ([10.97.216.204]) by ipoani.tcif.telstra.com.au with ESMTP; 11 May 2010 10:36:42 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,5978"; a="1787679"
Received: from wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) by ipcbni.tcif.telstra.com.au with ESMTP; 11 May 2010 10:36:42 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3756.srv.dir.telstra.com ([172.49.40.84]) with mapi; Tue, 11 May 2010 10:36:41 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Marius Scurtescu <mscurtescu@google.com>
Date: Tue, 11 May 2010 10:36:39 +1000
Thread-Topic: [OAUTH-WG] SWT for indicating sites where a token is valid
Thread-Index: Acrwm7ILVrA/+RI5RBm8dGkNOu2+sgAAB4nA
Message-ID: <255B9BB34FB7D647A506DC292726F6E1126328531E@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> <AANLkTimgXfVZc5-51FPsamrQPhj8EyXIeAa5qpQFhe3S@mail.gmail.com>
In-Reply-To: <AANLkTimgXfVZc5-51FPsamrQPhj8EyXIeAa5qpQFhe3S@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
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: Tue, 11 May 2010 00:36:54 -0000

Marius,

> But then again, how does the client end up making a request to
the wrong site?

The client follows a redirect or link. It doesn't know if the ultimate source of the new URI was the resource server’s internal logic, user-generated content, or a parameter in the request URI (eg an open redirector).


>> 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.

"sites" does help. If its value was:
  "sites": ["https://api.example.com", "https://img.example.com"]
Then no HTTP URI matches so the token is never sent in the clear.

--
James Manger

v2.23.0 | Report a Bug | By Email