IETF Logo Mail Archive

Re: [OAUTH-WG] problem statement

"Manger, James H" <James.H.Manger@team.telstra.com> Wed, 07 September 2011 03:51 UTC

Return-Path: <James.H.Manger@team.telstra.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 ABD7021F8DA3 for <oauth@ietfa.amsl.com>; Tue, 6 Sep 2011 20:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.325
X-Spam-Level:
X-Spam-Status: No, score=-3.325 tagged_above=-999 required=5 tests=[AWL=-2.424, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
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 QQjJ-7ZIRI0w for <oauth@ietfa.amsl.com>; Tue, 6 Sep 2011 20:51:15 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by ietfa.amsl.com (Postfix) with ESMTP id CFB4221F8D45 for <oauth@ietf.org>; Tue, 6 Sep 2011 20:51:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.68,343,1312120800"; d="scan'208";a="45178623"
Received: from unknown (HELO ipcavi.tcif.telstra.com.au) ([10.97.217.200]) by ipobvi.tcif.telstra.com.au with ESMTP; 07 Sep 2011 13:52:44 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6461"; a="36340485"
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipcavi.tcif.telstra.com.au with ESMTP; 07 Sep 2011 13:52:44 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3705.srv.dir.telstra.com ([172.49.40.203]) with mapi; Wed, 7 Sep 2011 13:52:43 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Michael Thomas <mike@mtcc.com>, "oauth@ietf.org" <oauth@ietf.org>
Date: Wed, 07 Sep 2011 13:52:41 +1000
Thread-Topic: [OAUTH-WG] problem statement
Thread-Index: AcxtAZcWUMDKVDxYROayx8MDCxxCCAADppjQ
Message-ID: <255B9BB34FB7D647A506DC292726F6E1128DF46CA4@WSMSG3153V.srv.dir.telstra.com>
References: <4E665B25.6090709@mtcc.com> <CD0B1909-8298-4CC3-B273-7B26E71EAB31@hueniverse.com> <4E666512.7010701@mtcc.com> <F4839FCD-CA73-4450-AD12-E07D46BB7746@hueniverse.com> <4E6667D1.3080404@mtcc.com> <1315334677.26387.YahooMailNeo@web31809.mail.mud.yahoo.com> <4E666B65.30701@mtcc.com> <29815937-0FB9-463B-B6E4-8FCAF7B3CD8C@hueniverse.com> <4E666E73.3050502@mtcc.com> <CAMrm-MJHKTxaj1iEm_Lr=X92sOiWZcYN4F6dNqb5w5gh4OPndQ@mail.gmail.com> <4E6671FA.3090503@gmail.com> <4E667469.2040007@mtcc.com> <1315337809.3136.38.camel@ground> <4E667953.9020906@mtcc.com> <71A460EE-1E2C-4165-99A8-5A97D6E9365C@jkemp.net> <4E667E2E.7090304@mtcc.com> <80A88920-A1EF-4A1C-A97E-F99379923CFB@jkemp.net> <4E66845E.7090906@mtcc.com> <E3DEC4C8-6BB0-44EE-821A-7589F5DC6462@jkemp.net> <4E669D3C.5000900@gmail.com> <4E66B964.2060808@stpeter.im> <4E66BFF0.9020008@gmail.com> <4E66C407.9090209@stpeter.im> <4E66C521.5070804@mtcc.com> <1315358847.25169.YahooMailNeo@web31809.mail.mud.yahoo.com> <4E66CF9A.8000905@mtcc.com>
In-Reply-To: <4E66CF9A.8000905@mtcc.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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] problem statement
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Wed, 07 Sep 2011 03:51:15 -0000

A strange aspects of this thread is that the current draft already talks about exactly this issue:

draft-ietf-oauth-v2-21 section 9 "Native Applications"

  "...Native applications can invoke an external user-agent or
  embed a user-agent within the application
  ...
  Embedded user-agents pose a security challenge because resource
  owners are authenticating in an unidentified window without access
  to the visual protections found in most external user-agents.
  Embedded user-agents educate end-user to trust unidentified
  requests for authentication (making phishing attacks easier to
  execute)."

The webView that Michael Thomas talks about is an "embedded user-agent".

--
James Manger


----------
From: oauth-bounces@ietf.org [mailto:oauth-bounces@ietf.org] On Behalf Of Michael Thomas

...
At this point, it would be just nice for the industry to know that the issue
even *exists*.

v2.23.0 | Report a Bug | By Email