IETF Logo Mail Archive

Re: [OAUTH-WG] why are we signing?

Brian Eaton <beaton@google.com> Fri, 13 November 2009 08:01 UTC

Return-Path: <beaton@google.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 034913A683D for <oauth@core3.amsl.com>; Fri, 13 Nov 2009 00:01:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.977
X-Spam-Level:
X-Spam-Status: No, score=-105.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 Buzwot8W-hk2 for <oauth@core3.amsl.com>; Fri, 13 Nov 2009 00:01:25 -0800 (PST)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.33.17]) by core3.amsl.com (Postfix) with ESMTP id 13B783A68DD for <oauth@ietf.org>; Fri, 13 Nov 2009 00:01:24 -0800 (PST)
Received: from zps37.corp.google.com (zps37.corp.google.com [172.25.146.37]) by smtp-out.google.com with ESMTP id nAD81ptJ024811 for <oauth@ietf.org>; Fri, 13 Nov 2009 08:01:53 GMT
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1258099313; bh=lsdVzfCXxhAyEhDfrfAhGDSuO/I=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=YL/zR2Wwsefec33QPc8Vt2R5OgcpS/uKXCac9KTBwqnpr8ksJPG7YgV+bqZdlqZzA iaefF6OH13Sw5VeR6IQsA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:x-system-of-record; b=eH3RPuh/RVeP/AH13wsyDh1KZg7jcVjYC0sNmFLNa/7tCdGUXxf2CwyEc4etkN41u P6OtNBfQIxDDoNxUxjgbA==
Received: from pxi29 (pxi29.prod.google.com [10.243.27.29]) by zps37.corp.google.com with ESMTP id nAD81lwS020731 for <oauth@ietf.org>; Fri, 13 Nov 2009 00:01:49 -0800
Received: by pxi29 with SMTP id 29so2129985pxi.1 for <oauth@ietf.org>; Fri, 13 Nov 2009 00:01:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.143.19 with SMTP id q19mr236797rvd.17.1258099307726; Fri, 13 Nov 2009 00:01:47 -0800 (PST)
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E72343785102E58@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <daf5b9570911082102u215dcf22gf0aeb2f3578e5ea0@mail.gmail.com> <35D50F5C-3982-4298-A9E0-86A528F5C5D3@jkemp.net> <daf5b9570911092158k682aff63l959c423c399b2277@mail.gmail.com> <4A956CE47D1066408D5C7EB34368A5110551FFC1@S4DE8PSAAQC.mitte.t-com.de> <daf5b9570911111754u49f72a0aia59814b5da497a51@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343785102B49@P3PW5EX1MB01.EX1.SECURESERVER.NET> <cb5f7a380911120745w2f576d1ej300723581e50f03f@mail.gmail.com> <90C41DD21FB7C64BB94121FBBC2E72343785102E58@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Fri, 13 Nov 2009 00:01:47 -0800
Message-ID: <daf5b9570911130001obdd3d4akf8be3276ee767ef6@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: Eran Hammer-Lahav <eran@hueniverse.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] why are we signing?
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: Fri, 13 Nov 2009 08:01:26 -0000

On Thu, Nov 12, 2009 at 11:18 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote:
> The body hash extension then extended the usefulness of the protocol to other payloads.

Careful how much faith you put in the body hash extension. =)  The
appendix has lots of caveats about how hard it is to deploy in
practice.  I don't expect most service providers to be able to do it.

v2.23.0 | Report a Bug | By Email