Re: [OAUTH-WG] Proposal: OAuth 1.0 signature in core with revision

Anthony Nadalin <> Mon, 27 September 2010 21:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1BE4E3A6DD8 for <>; Mon, 27 Sep 2010 14:38:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -10.238
X-Spam-Status: No, score=-10.238 tagged_above=-999 required=5 tests=[AWL=0.360, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id R7m9slzyvoEx for <>; Mon, 27 Sep 2010 14:38:05 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3C3E03A6DC7 for <>; Mon, 27 Sep 2010 14:37:19 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Mon, 27 Sep 2010 14:37:49 -0700
Received: from ([]) by ([]) with mapi id 14.01.0218.012; Mon, 27 Sep 2010 14:37:49 -0700
From: Anthony Nadalin <>
To: Eran Hammer-Lahav <>, "OAuth WG (" <>
Thread-Topic: Proposal: OAuth 1.0 signature in core with revision
Thread-Index: ActeDoaUK2WoVUKmSgyhimH2rZiaMgAfVOew
Date: Mon, 27 Sep 2010 21:37:49 +0000
Message-ID: <>
References: <90C41DD21FB7C64BB94121FBBC2E72343D45D80139@P3PW5EX1MB01.EX1.SECURESERVER.NET>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343D45D80139@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_1990A18DEA6E97429CFD1B4D2C5DA7E70CEB7DTK5EX14MBXC101red_"
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Proposal: OAuth 1.0 signature in core with revision
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: Mon, 27 Sep 2010 21:38:37 -0000

Not seeing an overwhelming support for doing this, how many interoperable deployments of 1.0a signature are there?

From: [] On Behalf Of Eran Hammer-Lahav
Sent: Sunday, September 26, 2010 11:44 PM
To: OAuth WG (
Subject: [OAUTH-WG] Proposal: OAuth 1.0 signature in core with revision

Building on John Panzer's proposal, I would like to ask if people have strong objections to the following:

- Add the 1.0a RFC language for HMAC-SHA-1 signatures to the core specification in -11
- Discuss the signature language on the list and improve both prose and signature base string construction
- Apply improvements to -12

Keeping the 1.0a signature in the core specification makes sense and builds on existing experience and deployment. If we can reach quick consensus on some improvements, great. If not, we satisfy the need of many here to offer a simple alternative to bearer tokens, without having to reach consensus on a new signature algorithm suitable for core inclusion.


I have seen nothing to suggest that this working group is going to reach consensus on a single signature algorithm worthy of core inclusion. I agree with John that at least the 1.0a algorithm is well understood and already deployed. I can live with it used without changes, which will also allow reusing existing code with 2.0. I think we can improve it by making small changes, but have better things to do with my time than spend the next few months arguing over it.

By including the 1.0a text in -11, we will have a feature complete specification that I hope many people here can live with if it doesn't change (which looks more likely).

My question is, who here has strong objections to this, and cannot live with the core specification including the 1.0a HMAC-SHA1 algorithm?