Re: [OAUTH-WG] Secure Client Token Storage
Eran Hammer-Lahav <eran@hueniverse.com> Wed, 18 November 2009 09:08 UTC
Return-Path: <eran@hueniverse.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 A6A653A68B4 for <oauth@core3.amsl.com>; Wed, 18 Nov 2009 01:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.624
X-Spam-Level:
X-Spam-Status: No, score=-1.624 tagged_above=-999 required=5 tests=[AWL=0.974, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 xeF-ajCS1-mU for <oauth@core3.amsl.com>; Wed, 18 Nov 2009 01:07:59 -0800 (PST)
Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id B52C83A6887 for <oauth@ietf.org>; Wed, 18 Nov 2009 01:07:59 -0800 (PST)
Received: (qmail 11742 invoked from network); 18 Nov 2009 05:07:53 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 18 Nov 2009 05:07:53 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.19]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Tue, 17 Nov 2009 22:07:53 -0700
From: Eran Hammer-Lahav <eran@hueniverse.com>
To: Joseph A Holsten <joseph@josephholsten.com>, "oauth@ietf.org" <oauth@ietf.org>
Date: Tue, 17 Nov 2009 22:07:41 -0700
Thread-Topic: [OAUTH-WG] Secure Client Token Storage
Thread-Index: AcpoAqDAHMthiE7eS4uXQeNCA1nHewACm0dY
Message-ID: <C728C11D.29773%eran@hueniverse.com>
In-Reply-To: <826F29F5-85AB-443B-8CAB-466EBE48AB8C@josephholsten.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C728C11D29773eranhueniversecom_"
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Secure Client Token Storage
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: Wed, 18 Nov 2009 09:08:03 -0000
Would you like to propose text? I think this is application specific. Isn't calling it a token *secret* enough? :-) EHL On 11/17/09 7:52 PM, "Joseph A Holsten" <joseph@josephholsten.com> wrote: If browsers start having OAuth support, they're definitely going to need a secure store for those OAuth tokens, so my malicious app doesn't just dig through your Firefox config for access to tokens. This doesn't seem to be mentioned in draft-hammer-oauth-05, §4.7 is server specific, and §4.8 only recommends to hide the client credentials. Should the spec add a section recommending clients store access tokens in secure storage? -- Joseph Holsten http://josephholsten.com mailto:joseph@josephholsten.com tel:+1-918-948-6747 _______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Secure Client Token Storage Joseph A Holsten
- Re: [OAUTH-WG] Secure Client Token Storage Joseph A Holsten
- Re: [OAUTH-WG] Secure Client Token Storage Eran Hammer-Lahav