Return-Path: 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 92D8B3A6851 for ; Thu, 23 Sep 2010 18:51:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.492 X-Spam-Level: X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.106, 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 Skmv3u-usxGl for ; Thu, 23 Sep 2010 18:51:00 -0700 (PDT) Received: from p3plex1out02.prod.phx3.secureserver.net (p3plex1out02.prod.phx3.secureserver.net [72.167.180.18]) by core3.amsl.com (Postfix) with SMTP id C1FAC3A6804 for ; Thu, 23 Sep 2010 18:51:00 -0700 (PDT) Received: (qmail 4883 invoked from network); 24 Sep 2010 01:51:31 -0000 Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.21) by p3plex1out02.prod.phx3.secureserver.net with SMTP; 24 Sep 2010 01:51:31 -0000 Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT003.EX1.SECURESERVER.NET ([72.167.180.21]) with mapi; Thu, 23 Sep 2010 18:51:31 -0700 From: Eran Hammer-Lahav To: Dirk Balfanz , OAuth WG Date: Thu, 23 Sep 2010 18:51:28 -0700 Thread-Topic: [OAUTH-WG] Signatures spec proposal, take 2 Thread-Index: ActbcDtRZ1a6oKB9Rgqp7eBGiF63tAAGsVZj Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_C8C152303AC67eranhueniversecom_" MIME-Version: 1.0 Subject: Re: [OAUTH-WG] Signatures spec proposal, take 2 X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Sep 2010 01:51:02 -0000 --_000_C8C152303AC67eranhueniversecom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In part II, how is the signature bound to the HTTP request URI? I see the m= ethod and body, but not the request URI. EHL On 9/23/10 3:39 PM, "Dirk Balfanz" wrote: Hi guys, sorry it took a while, but here is an updated proposal. It's still in three= parts: Part I is about "JSON Tokens" that can be used for all sorts of things, not= just OAuth: http://balfanz.github.com/jsontoken-spec/draft-balfanz-jsontoken-00.html Part II is about how to embed an OAuth token and (some parts of) an HTTP re= quest into a JSON Token: http://balfanz.github.com/jsontoken-spec/draft-balfanz-signedoauth2-00.html Part III is how to use signatures instead of client secrets for assertions = in OAuth: http://balfanz.github.com/jsontoken-spec/draft-balfanz-clientassertions-00.= html Diffs from the last specs are: - JSON Tokens are now just a profile of Magic Signatures, which John Panzer= has helpfully extended for this purpose - There was a vulnerability to masquerading attacks in the last proposal, w= hich is addressed in this proposal by adding a data_type parameter that is = part of the signature, but _not_ part of the payload. - no more support of X.509 certs - the only supported format for discovered= public keys is now the Magic Key format. We'll give people tools (which ar= e quite easy to write) to convert their self-signed or CA-issued certs to m= agic keys. - The specs are now formatted as I-Ds. Comments, please! Dirk. --_000_C8C152303AC67eranhueniversecom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: [OAUTH-WG] Signatures spec proposal, take 2 In part II, how is the signature bound to the HTTP request URI? I see= the method and body, but not the request URI.

EHL


On 9/23/10 3:39 PM, "Dirk Balfanz" <balfanz@google.com> wrote:

Hi guys,=A0

sorry it took a while, but here is an updated proposal. It's still in three= parts:

Part I is about "JSON Tokens" that can be used for all sorts of t= hings, not just OAuth:
http://balfanz.github.com/jsontoken-spec/draft-balfanz-js= ontoken-00.html

Part II is about how to embed an OAuth token and (some parts of) an HTTP re= quest into a JSON Token:
http://balfanz.github.com/jsontoken-spec/draft-balfanz-signedo= auth2-00.html

Part III is how to use signatures instead of client secrets for assertions = in OAuth:
http://balfanz.github.com/jsontoken-spec/draft-balfanz-cli= entassertions-00.html

Diffs from the last specs are:

- JSON Tokens are now just a profile of Magic Signatures, which John Panzer= has helpfully extended for this purpose
- There was a vulnerability to masquerading attacks in the last proposal, w= hich is addressed in this proposal by adding a data_type parameter that is = part of the signature, but _not_ part of the payload.
- no more support of X.509 certs - the only supported format for discovered= public keys is now the Magic Key format. We'll give people tools (which ar= e quite easy to write) to convert their self-signed or CA-issued certs to m= agic keys.
- The specs are now formatted as I-Ds.

Comments, please!

Dirk.


--_000_C8C152303AC67eranhueniversecom_--