Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-security-topics-14.txt
Vladimir Dzhuvinov <vladimir@connect2id.com> Wed, 12 February 2020 18:36 UTC
Return-Path: <vladimir@connect2id.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 881C0120A28 for <oauth@ietfa.amsl.com>; Wed, 12 Feb 2020 10:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.875
X-Spam-Level:
X-Spam-Status: No, score=-0.875 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 Ok7OeXlILUha for <oauth@ietfa.amsl.com>; Wed, 12 Feb 2020 10:36:36 -0800 (PST)
Received: from p3plsmtpa07-02.prod.phx3.secureserver.net (p3plsmtpa07-02.prod.phx3.secureserver.net [173.201.192.231]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09522120A1D for <oauth@ietf.org>; Wed, 12 Feb 2020 10:36:35 -0800 (PST)
Received: from [192.168.88.241] ([94.155.17.54]) by :SMTPAUTH: with ESMTPSA id 1wsDjjzrtshfx1wsEjv6M1; Wed, 12 Feb 2020 11:36:35 -0700
X-CMAE-Analysis: v=2.3 cv=Rty70xuK c=1 sm=1 tr=0 a=FNQ4XmqxRr20pcroDK0mpg==:117 a=FNQ4XmqxRr20pcroDK0mpg==:17 a=jpOVt7BSZ2e4Z31A5e1TngXxSK0=:19 a=9cW_t1CCXrUA:10 a=q0rX5H01Qin5IyBaTmIA:9 a=r77TgQKjGQsHNAKrUKIA:9 a=__SxRlIrAAAA:8 a=48vgC7mUAAAA:8 a=DCeuyAmqCDnMODE0U_oA:9 a=QEXdDO2ut3YA:10 a=pGLkceISAAAA:8 a=esGgMcD7aKpODhBHuI0A:9 a=TRcCxHA2z9OZbpZW:21 a=_W_S_7VecoQA:10 a=D8lnhvtxf0AONpHuB7QA:9 a=ZVk8-NSrHBgA:10 a=30ssDGKg3p0A:10 a=H5r4HjhRfVyZ-DhAOYba:22 a=w1C3t2QeGrPiZgrLijVG:22
X-SECURESERVER-ACCT: vladimir@connect2id.com
Cc: oauth <oauth@ietf.org>
References: <158135846124.3970.5036541129625161720@ietfa.amsl.com> <0f312b87-7721-e8c1-30ef-b6cb7416248b@connect2id.com> <CA+k3eCRfpHQouAECdt6vgkqWZNX0OGaQew2Z+tsHa-jmL-Ty+Q@mail.gmail.com>
From: Vladimir Dzhuvinov <vladimir@connect2id.com>
Organization: Connect2id Ltd.
Message-ID: <9eac3c6f-ec5a-25ce-1ef7-b9883aa52224@connect2id.com>
Date: Wed, 12 Feb 2020 20:36:32 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <CA+k3eCRfpHQouAECdt6vgkqWZNX0OGaQew2Z+tsHa-jmL-Ty+Q@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms060300020403090905030409"
X-CMAE-Envelope: MS4wfP1OSs/QTCETOfNSvq2JcikZC95PgtcNDbWIz+bVLp8tGFqGn61nLFiiEXMKBloUbP7iBjtQCNsnMqzY4V4uNcrbDPncPvhwsk+HakHk3Wazz8J7QtJF +/VibTSsg43+edkXnUO+NVs3XCKXj3n0xF0pqRL5wz/d9tjFT8b65bkU
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/enApUPlLth5-AZ6M2whDZs3CIC4>
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-security-topics-14.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 12 Feb 2020 18:36:38 -0000
Thanks Brian, we missed that entirely. Have there been any thoughts on specifying a matching client reg parameter for PKCE? Vladimir On 12/02/2020 01:19, Brian Campbell wrote: > code_challenge_methods_supported is/was already defined in RFC 8414, > it's just kinda easy to miss that it's there as you'd typically expect > to find that sort of thing in the doc that defines PKCE itself. But > PKCE (RFC 7636) predates AS metadata (RFC 8414) so things are > different in that case. > > I notice too that draft-ietf-oauth-security-topics-14 still > erroneously has RFC 8418 as the reference next to > code_challenge_methods_supported where it should be RFC 8414. > > On Tue, Feb 11, 2020 at 11:43 AM Vladimir Dzhuvinov > <vladimir@connect2id.com <mailto:vladimir@connect2id.com>> wrote: > > Fantastic, we now have "code_challenge_methods_supported" defined > for AS > metadata and it's a MUST. Long overdue. > > Vladimir > > On 10/02/2020 20:14, internet-drafts@ietf.org > <mailto:internet-drafts@ietf.org> wrote: > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > > This draft is a work item of the Web Authorization Protocol WG > of the IETF. > > > > Title : OAuth 2.0 Security Best Current Practice > > Authors : Torsten Lodderstedt > > John Bradley > > Andrey Labunets > > Daniel Fett > > Filename : draft-ietf-oauth-security-topics-14.txt > > Pages : 46 > > Date : 2020-02-10 > > > > Abstract: > > This document describes best current security practice for > OAuth 2.0. > > It updates and extends the OAuth 2.0 Security Threat Model to > > incorporate practical experiences gathered since OAuth 2.0 was > > published and covers new threats relevant due to the broader > > application of OAuth 2.0. > > > > > > The IETF datatracker status page for this draft is: > > https://datatracker.ietf.org/doc/draft-ietf-oauth-security-topics/ > > > > There are also htmlized versions available at: > > https://tools.ietf.org/html/draft-ietf-oauth-security-topics-14 > > > https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics-14 > > > > A diff from the previous version is available at: > > > https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-security-topics-14 > > > > > > Please note that it may take a couple of minutes from the time > of submission > > until the htmlized version and diff are available at > tools.ietf.org <http://tools.ietf.org>. > > > > Internet-Drafts are also available by anonymous FTP at: > > ftp://ftp.ietf.org/internet-drafts/ > > > > _______________________________________________ > > > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org <mailto:OAuth@ietf.org> > https://www.ietf.org/mailman/listinfo/oauth >
- [OAUTH-WG] I-D Action: draft-ietf-oauth-security-… internet-drafts
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-secur… Vladimir Dzhuvinov
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-secur… Brian Campbell
- Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-secur… Vladimir Dzhuvinov