IETF Logo Mail Archive

Re: [OAUTH-WG] Signatures, Why?

Brian Eaton <beaton@google.com> Tue, 16 March 2010 06:28 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 940173A68EA for <oauth@core3.amsl.com>; Mon, 15 Mar 2010 23:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.964
X-Spam-Level:
X-Spam-Status: No, score=-105.964 tagged_above=-999 required=5 tests=[AWL=0.013, 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 fVpgVlfP-V-f for <oauth@core3.amsl.com>; Mon, 15 Mar 2010 23:28:04 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id B01013A683C for <oauth@ietf.org>; Mon, 15 Mar 2010 23:28:04 -0700 (PDT)
Received: from wpaz5.hot.corp.google.com (wpaz5.hot.corp.google.com [172.24.198.69]) by smtp-out.google.com with ESMTP id o2G6SAw6001202 for <oauth@ietf.org>; Mon, 15 Mar 2010 23:28:10 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1268720890; bh=1A/FqT/ffTtrPeTvnUxFanT0+sI=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=ZuM4Y0W7qsX0dTR0GLzkzLhstLUfBAkxW0W8Pi4yZD1dyLc1bAYK8NzFlOL5ynUDY HlvbF5vspWtu6O4Nk30aw==
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=Syd2mjlVedOYcmeRVL5mzBKUnJQnf1PQHUS+AyyTTZ1uhLbvQQaXFt2vfbKHjK2xk ttxqryob/nkpVMEFoq7Dw==
Received: from vws8 (vws8.prod.google.com [10.241.21.136]) by wpaz5.hot.corp.google.com with ESMTP id o2G6S9Ir025964 for <oauth@ietf.org>; Mon, 15 Mar 2010 23:28:09 -0700
Received: by vws8 with SMTP id 8so422452vws.9 for <oauth@ietf.org>; Mon, 15 Mar 2010 23:28:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.89.195 with SMTP id f3mr8076vcm.138.1268720888822; Mon, 15 Mar 2010 23:28:08 -0700 (PDT)
In-Reply-To: <cb5f7a381003152322m5c6ec744nb8336e329860439e@mail.gmail.com>
References: <d37b4b431003041200n1fc6cc5au83194aca28763b0d@mail.gmail.com> <4B99B2DD.3000405@stpeter.im> <4B99D783.1090905@lodderstedt.net> <4B9EB99F.1050609@lodderstedt.net> <cb5f7a381003152322m5c6ec744nb8336e329860439e@mail.gmail.com>
Date: Mon, 15 Mar 2010 23:28:08 -0700
Message-ID: <daf5b9571003152328y6362787ah1c5d90a0a7ac2bd6@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: John Panzer <jpanzer@google.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
Cc: oauth@ietf.org
Subject: Re: [OAUTH-WG] Signatures, Why?
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: Tue, 16 Mar 2010 06:28:05 -0000

On Mon, Mar 15, 2010 at 11:22 PM, John Panzer <jpanzer@google.com> wrote:
> I would like to see at least one concrete proposal that will
> accomplish this.

I think this goes for pretty much any of the requirements that have
been discussed. =)

v2.23.0 | Report a Bug | By Email