Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Mix-Up Mitigation

Nat Sakimura <sakimura@gmail.com> Mon, 25 January 2016 22:58 UTC

Return-Path: <sakimura@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B98081A1BB9 for <oauth@ietfa.amsl.com>; Mon, 25 Jan 2016 14:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HZ4J3JzSdVns for <oauth@ietfa.amsl.com>; Mon, 25 Jan 2016 14:58:55 -0800 (PST)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8C141A1BA9 for <oauth@ietf.org>; Mon, 25 Jan 2016 14:58:54 -0800 (PST)
Received: by mail-qg0-x231.google.com with SMTP id e32so122124470qgf.3 for <oauth@ietf.org>; Mon, 25 Jan 2016 14:58:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=idEewZHzD0Rh2UC8AMBhSxnux+KCd2u22mOXSUxULug=; b=RHjGroou6UhWzzPv29D2aVotPxn+pmHgagBbQM6PxEyeJDoRkQc/PrejzSisH82iiJ KQGVrzeoN8gpKSmIQkJxxRIn5NDXPcgQEjyPReNt0/INkKP+HR4tCbGTNTp9aKT+0Xz0 wXrFvpXJK2gs14idHAoOP7rpovseN3+wHcgQMcGyMdz+zhKAvTpXnI/NrMOzM94Ylmnb l2VfN4g/yUe5Nwx8gxOcd+JtChaSQuOpckfigTilLmnQLHJCVLUrgrlidhtUnIOn+dE5 GZ1ic3L1E4+yRGWHPV5x48WcAdSGiUIgIevDqn9SNo4m5BsaqpSl7L54ubU2OgkwKMuz 7F/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-type; bh=idEewZHzD0Rh2UC8AMBhSxnux+KCd2u22mOXSUxULug=; b=O3xwx5awNniLFJ46p7VGOYmJXNCyzu9FJmJChClfqg0jVHAaJzJxLtyXqT0/ETNJZq qNX+eMBOfLIy5Ou/Pq9ilPc9aKGcLpGc6TKRNTuOjI65QSmUZQh/qeMgY5vsjvKNGSbP PP/Sp+xNBXxFtCs3qfBUO+jvKtSucgT3fQvhiJcAC/rCN+sz4R09fQq+rTIGcZqJLEAf FUmyb9qO+cN7yTGdS7hXA0l/igK4zNH+Y9xfLJa+wik+Bz9qo8Z0chJnoDvACubZk3AE c5YRi41TzyfjksTXs06+Q4oa7uMwYm/PAuf1FiPWT4bEcPYB7wSPoDqPWqFyMYyIMVeV Ad3A==
X-Gm-Message-State: AG10YOTU+hgp/Gwl3s84+T7t2HDb6Ib/Apovx0CD7ozU2EH9CI0Gojd3r/5YjHp6nB+vP1uEwDADsULzHNjs8Q==
X-Received: by 10.140.18.136 with SMTP id 8mr24304109qgf.64.1453762734171; Mon, 25 Jan 2016 14:58:54 -0800 (PST)
MIME-Version: 1.0
References: <569E22E1.5010402@gmx.net> <CANSMLKHjAHr6rUZny5EkX0KBHnOcLuUOZBL0Wwf6V8Y3tt_kNw@mail.gmail.com> <CABzCy2C-_57dO5n6GN6wazA9ozuPivrQd95g_XvdkPWx6zDwAA@mail.gmail.com> <CANSMLKE98FVdDV-7bwW3wZ=-ao5=oXkn9LO5s_M1KmMAt7Drcw@mail.gmail.com> <537B9D13-1159-4B2D-9E1A-A245C9B3659C@ve7jtb.com> <CAAP42hDUciKpS51dyx7Zy-kSCB_JUZqooXiaGTopHaFr_QkF5Q@mail.gmail.com> <995474C5-62E7-4310-84AF-A5EF1CDEA4DB@ve7jtb.com> <56A63F82.40104@aol.com> <6D8FA56F-EA72-4509-90C1-DC33094FA695@ve7jtb.com> <56A66522.1090804@aol.com> <23E34900-5C05-4295-AFC5-7DEBA6449AA7@ve7jtb.com> <56A66BED.3090505@aol.com> <8EBCD2DD-D9D8-4AFD-A12F-A8C5C9DC4C06@oracle.com>
In-Reply-To: <8EBCD2DD-D9D8-4AFD-A12F-A8C5C9DC4C06@oracle.com>
From: Nat Sakimura <sakimura@gmail.com>
Date: Mon, 25 Jan 2016 22:58:44 +0000
Message-ID: <CABzCy2BV6wWPffpyGBw71LoYe1BYppBkmXgrX2NwMaDw_3WK5g@mail.gmail.com>
To: "Phil Hunt (IDM)" <phil.hunt@oracle.com>, George Fletcher <gffletch@aol.com>
Content-Type: multipart/alternative; boundary=001a113546425bb579052a308309
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/FOz6vDtUcuhgslQ-AeVXc-aU8S0>
Cc: "oauth@ietf.org WG" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Call for Adoption: OAuth 2.0 Mix-Up Mitigation
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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, 25 Jan 2016 22:58:56 -0000

Hi Phil,

Since I was not in Darmstadt, I really do not know what was discussed
there, but with the compromised developer documentation described in
http://nat.sakimura.org/2016/01/15/idp-mix-up-attack-on-oauth-rfc6749/, all
RFC6749 clients with a naive implementer will be affected. The client does
not need to be talking to multiple IdPs.

Nat

2016年1月26日(火) 3:58 Phil Hunt (IDM) <phil.hunt@oracle.com>om>:

> I recall making this point in Germany. 99% of existing use is fine. OIDC
> is probably the largest community that *might* have an issue.
>
> I recall proposing a new security document that covers oauth security for
> dynamic scenarios. "Dynamic" being broadly defined to mean:
> * clients who have configured at runtime or install time (including
> clients that do discovery)
> * clients that communicate with more than one endpoint
> * clients that are deployed in large volume and may update frequently
> (more discussion of "public" cases)
> * clients that are script based (loaded into browser on the fly)
> * others?
>
> Phil
>
> > On Jan 25, 2016, at 10:39, George Fletcher <gffletch@aol.com> wrote:
> >
> > would
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>