IETF Logo Mail Archive

Re: [OAUTH-WG] OAuth2 security considerations for client_id

William Mills <wmills@yahoo-inc.com> Fri, 06 January 2012 18:24 UTC

Return-Path: <wmills@yahoo-inc.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 1109621F85BD for <oauth@ietfa.amsl.com>; Fri, 6 Jan 2012 10:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.241
X-Spam-Level:
X-Spam-Status: No, score=-17.241 tagged_above=-999 required=5 tests=[AWL=0.357, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_DEF_WHITELIST=-15]
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 Nt56CsRtnnyb for <oauth@ietfa.amsl.com>; Fri, 6 Jan 2012 10:24:28 -0800 (PST)
Received: from nm15.bullet.mail.sp2.yahoo.com (nm15.bullet.mail.sp2.yahoo.com [98.139.91.85]) by ietfa.amsl.com (Postfix) with SMTP id CE99621F84EB for <oauth@ietf.org>; Fri, 6 Jan 2012 10:24:28 -0800 (PST)
Received: from [98.139.91.69] by nm15.bullet.mail.sp2.yahoo.com with NNFMP; 06 Jan 2012 18:24:28 -0000
Received: from [98.139.91.42] by tm9.bullet.mail.sp2.yahoo.com with NNFMP; 06 Jan 2012 18:24:28 -0000
Received: from [127.0.0.1] by omp1042.mail.sp2.yahoo.com with NNFMP; 06 Jan 2012 18:24:28 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 745492.83603.bm@omp1042.mail.sp2.yahoo.com
Received: (qmail 25561 invoked by uid 60001); 6 Jan 2012 18:24:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo-inc.com; s=ginc1024; t=1325874268; bh=XCBK3h2GpU4ZQgkETPzvttYTIi2qYITcd1V+2Ptkgos=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=W74WlPG2fkOlC7FRu0KHX8ProRO6JMuLZdBxQOKHwC9ag1H4UQExVNxY73Ewv0pXEtaz0CyYl+2REpVmYsDoXvTKuYIwfYVdhgyYbtxG5LYRL6HUbwmSolo4YavmWJjlClTvZW+6GBDlv/6+x9bL5QjLlciWq5m/9YoGE0QASA8=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ginc1024; d=yahoo-inc.com; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=ZsrBBxMGw/TKnwwOjMXPvu1X6QiwDRUbnz7SBeABMhqlIoelevVHgi2ptKM+e5cWZGIsGap1In7kPD+zgyi3zTCCf0UI5nrVF8v1JtRJuCMtMIDfKe4bnQ010zejGu0cVSDPHX2A1KcJkOOOdLdgpcbDddHc1EqhAkQD7AU9rYM=;
X-YMail-OSG: lkrKetAVM1lOPHzCDY36NMRrFGivRFWfizIs30iZ_WkjFhp lRZQVmnLIDQED4BHT4Pu_YNKSr04A2pztU8xCEfesHUrE4QgF_JJDI0OY1fM c7JtOshlbt.8Ves2D5JDMTPef3Cb9xSZbkK6sJFC0xdQMrtycRSJe.h2MJeA 9JQhcEWnIo2oj4t0mCP8WNIBNy0jR6wQix.BqYGC0w_bLGK_720LPJL0jOqi Hso0Zqm7B_l.nKrBWXRv.rAKYS36Ps6XxHwcQIpHYnmFi6_hGkvrD73RODHG 4UGJzI21t1JOXLWFSbR5Zfsy5g.QF2.Y942xsDzVkpDmT3nCoorIKSmVrdrK GH22dV94h361oxesPpknBFMDKQ6kvJiHcw31T1uvZ7X5imWi8zNGaUTwoOSP JaIDja7gtpEdGXURngU6QN3vGKK2O2SMV8IsS2g--
Received: from [209.131.62.115] by web31807.mail.mud.yahoo.com via HTTP; Fri, 06 Jan 2012 10:24:28 PST
X-RocketYMMF: william_john_mills
X-Mailer: YahooMailWebService/0.8.116.331537
References: <CACHRFsBNqUgXPxgFth-zHL=tvkVHy=OCXK2tcQ6hC273eoJ9EQ@mail.gmail.com> <0f4aff4b-9fcc-4077-9fca-a068ebf97dd4@email.android.com> <1325871268.64118.YahooMailNeo@web31809.mail.mud.yahoo.com> <4F0733E6.2000308@gmail.com>
Message-ID: <1325874268.38071.YahooMailNeo@web31807.mail.mud.yahoo.com>
Date: Fri, 06 Jan 2012 10:24:28 -0800
From: William Mills <wmills@yahoo-inc.com>
To: Paul Madsen <paul.madsen@gmail.com>
In-Reply-To: <4F0733E6.2000308@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-125733401-1557728781-1325874268=:38071"
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] OAuth2 security considerations for client_id
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: William Mills <wmills@yahoo-inc.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: Fri, 06 Jan 2012 18:24:30 -0000

Yeah, I sure did.  Client ID being the moral equivalent of user agent string in a browser.



________________________________
 From: Paul Madsen <paul.madsen@gmail.com>
To: William Mills <wmills@yahoo-inc.com> 
Cc: Torsten Lodderstedt <torsten@lodderstedt.net>; Karim <medkarim.esskalli@gmail.com>; "oauth@ietf.org" <oauth@ietf.org> 
Sent: Friday, January 6, 2012 9:48 AM
Subject: Re: [OAUTH-WG] OAuth2 security considerations for client_id
 

William, presumably you meant 'client_secret'?

And is it fair to say that this reflects the current reality (of app
    distribution channels & OS protections) more so than any
    inherent mobile client limitation?

paul

On 1/6/12 12:34 PM, William Mills wrote: 
Yeah, certainly for Mobile clients this is true.  There are classes of clients (server to server implementations notably) where clientID can be a proper secret and be usefule for client validation.
>
>
>
>
>________________________________
> From: Torsten Lodderstedt <torsten@lodderstedt.net>
>To: Karim <medkarim.esskalli@gmail.com>; oauth@ietf.org 
>Sent: Friday, January 6, 2012 5:21 AM
>Subject: Re: [OAUTH-WG] OAuth2 security considerations for client_id
> 
>
>Hi,
>
>your observation is correct. OAuth security considerations
              recommend not to rely on secrets for authenticating mobile
              apps (aka native apps) but to manage them as so-called
              public clients. Please take a look onto section 10 of the
              core spec for further details.
>
>regards,
>Torsten.
>
>
>
>
>Karim <medkarim.esskalli@gmail.com> schrieb: 
>Hello,
>>
>>
>>When using User-agent flow with OAuth2 for mobile platform, there is no way for Authorization server to authenticate the client_id of the application.
>>
>>
>>So, anyone can impersonate my app by copying the client_id (and so get all access tokens on my behalf), and this is applicable to Facebook, Foursquare,...
>>
>>
>>This is not managed by OAuth2 ? Or I missed something ?
>>
>>
>>For Web applications (Web server flow), access token is stored on the server side, and the client is authenticated using secret key.
>>
>>
-- 
>>Karim
>>
>>
>_______________________________________________
>OAuth mailing list
>OAuth@ietf.org
>https://www.ietf.org/mailman/listinfo/oauth
>
>
>
>
>
>_______________________________________________
OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email