[OAUTH-WG] Twitter signature delegation use case
David Recordon <recordond@gmail.com> Fri, 12 March 2010 20:42 UTC
Return-Path: <recordond@gmail.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 C995C3A68BA for <oauth@core3.amsl.com>; Fri, 12 Mar 2010 12:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, 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 KHJf8yEVCSz0 for <oauth@core3.amsl.com>; Fri, 12 Mar 2010 12:42:19 -0800 (PST)
Received: from mail-iw0-f186.google.com (mail-iw0-f186.google.com [209.85.223.186]) by core3.amsl.com (Postfix) with ESMTP id 3FCE03A6881 for <oauth@ietf.org>; Fri, 12 Mar 2010 12:42:19 -0800 (PST)
Received: by iwn16 with SMTP id 16so501970iwn.31 for <oauth@ietf.org>; Fri, 12 Mar 2010 12:42:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=bHIL5hWEo8cuLF2hzHsKmch62MuUxL/Lal4pvm4hkgc=; b=TqFFKrhwlN/l+7GL/TntAyc8ETn3/3zhDhrFMrrRqQcq+C4QNbfuWMhJjKXT2f+69F 7v5s0XJURJhBEk4QqoNu7EiJ6LMuhldp7NZHFiRTsisO8VqNwNJZLGzWurWEBgqTXVUE dnwFJG5t81cot63H4y4jpiCK+SqhwoDaZl1dY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=Wlt4IJENyPP+L+D50Z/NzoBAp/B4c/eSjgLuo0IQEkTMHZgVvCOYIK2Nk/TQJXjiol EydMihht+azLLckrUN1h/o4rTuQJ4cNjcRyeqja50hv++SRXtKOPIk/Skw9ZywB1M00H JJTszMS6nzXshYfrcf59NcG+b2qmeZDWCjlPw=
MIME-Version: 1.0
Received: by 10.231.143.12 with SMTP id s12mr593464ibu.38.1268426542094; Fri, 12 Mar 2010 12:42:22 -0800 (PST)
Date: Fri, 12 Mar 2010 12:42:21 -0800
Message-ID: <fd6741651003121242n5b24ef4cib75b4357e1a0f62@mail.gmail.com>
From: David Recordon <recordond@gmail.com>
To: OAuth WG <oauth@ietf.org>
Content-Type: multipart/mixed; boundary="0016e65ae5d6771d520481a091b8"
Cc: Raffi Krikorian <raffi@twitter.com>
Subject: [OAUTH-WG] Twitter signature delegation use case
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, 12 Mar 2010 20:42:20 -0000
Was catching up with Raffi from Twitter yesterday and he pointed me to http://mehack.com/oauth-echo-delegation-in-identity-verificatio. PDF also attached.
- [OAUTH-WG] Twitter signature delegation use case David Recordon
- Re: [OAUTH-WG] Twitter signature delegation use c… Brian Eaton