IETF Logo Mail Archive

[OAUTH-WG] security considerations - authorization tokens

Brian Eaton <beaton@google.com> Mon, 23 May 2011 03:47 UTC

Return-Path: <beaton@google.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04C0BE0720 for <oauth@ietfa.amsl.com>; Sun, 22 May 2011 20:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.977
X-Spam-Level:
X-Spam-Status: No, score=-106.977 tagged_above=-999 required=5 tests=[AWL=-1.000, 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ldt5crNrImt9 for <oauth@ietfa.amsl.com>; Sun, 22 May 2011 20:47:10 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.67]) by ietfa.amsl.com (Postfix) with ESMTP id 7F25DE071E for <oauth@ietf.org>; Sun, 22 May 2011 20:47:09 -0700 (PDT)
Received: from kpbe11.cbf.corp.google.com (kpbe11.cbf.corp.google.com [172.25.105.75]) by smtp-out.google.com with ESMTP id p4N3l7Pe009705 for <oauth@ietf.org>; Sun, 22 May 2011 20:47:08 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1306122428; bh=J5Z61hs6mYEMLHG9qDYBRFbG6DE=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=k4yWPEZbJvjEmjg3dqP9z2PQiLM3UK+Bkp1OsCICzMBuRnykTbeb/sytmqsImvIw+ +lqShsHYVbgKH2nk2qeDA==
Received: from pva4 (pva4.prod.google.com [10.241.209.4]) by kpbe11.cbf.corp.google.com with ESMTP id p4N3l6fn015079 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <oauth@ietf.org>; Sun, 22 May 2011 20:47:06 -0700
Received: by pva4 with SMTP id 4so3163544pva.2 for <oauth@ietf.org>; Sun, 22 May 2011 20:47:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=HgZ8vdJ27sH5OJT0VtDIO7PzdrVfwfzq4AUJuwhnj0s=; b=pr11SEsslkfPKVDeLZ2N3sZBBzAoHdNn/BbGygVP6DBJMisDgHfmYXFWA26xFHamRO HV52gN5Hn0fhcWYmbPaA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:date:message-id:subject:from:to:content-type; b=bGuGLaJg4EhA8+lwZaA3gwmaRfBLmCsiX9UBhpPzhnc0AOlJK3gu8itMTZDKgcwmd0 70e3ay9z4doOzY/+nKxw==
MIME-Version: 1.0
Received: by 10.142.221.1 with SMTP id t1mr742387wfg.437.1306122426048; Sun, 22 May 2011 20:47:06 -0700 (PDT)
Received: by 10.142.14.2 with HTTP; Sun, 22 May 2011 20:47:05 -0700 (PDT)
Date: Sun, 22 May 2011 20:47:05 -0700
Message-ID: <BANLkTiktC8z60OyKxJHTnqGb4o5h7OSJeg@mail.gmail.com>
From: Brian Eaton <beaton@google.com>
To: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/mixed; boundary="000e0cd146963ce08204a3e95354"
X-System-Of-Record: true
Subject: [OAUTH-WG] security considerations - authorization tokens
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 23 May 2011 03:47:11 -0000

As I said in the other note, after reading through the security
considerations section a couple of times, I think it could benefit
from a different organization.  Specifically

- keep the introduction, it’s awesome.
- write new sections for each of the following
   1) Authorization Tokens
   2) Web Application Clients
   3) User-Agent Clients
   4) Installed Application Clients
   5) Authorization Servers
   6) Resource Servers
- merge the current text into the appropriate sections.

I took a swing at the authorization tokens text.  I tried to capture
most of the relevant items from the current draft, but might have
missed some.

Cheers,
Brian

v2.23.0 | Report a Bug | By Email