Re: [OAUTH-WG] Small error in OAuth BCP and new 2.1 draft...
Daniel Fett <fett@danielfett.de> Thu, 12 March 2020 13:39 UTC
Return-Path: <fett@danielfett.de>
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 302163A08C7 for <oauth@ietfa.amsl.com>; Thu, 12 Mar 2020 06:39:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_NONE=0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=danielfett.de
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 5xpWU9w1Vj9l for <oauth@ietfa.amsl.com>; Thu, 12 Mar 2020 06:39:33 -0700 (PDT)
Received: from d3f.me (redstone.d3f.me [5.9.29.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89A343A08A9 for <oauth@ietf.org>; Thu, 12 Mar 2020 06:39:33 -0700 (PDT)
Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by d3f.me (Postfix) with ESMTPA id 0FBC06713 for <oauth@ietf.org>; Thu, 12 Mar 2020 13:39:30 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de; s=dkim; t=1584020371; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=8xl8wCt9ETmmtoq6tQRJTRghNLEQKSwQwV2zvcVvnw4=; b=qf/afcYiCzLdnAVWvHluWNMutaG1nr3ke0BD48gJsweGsMrLb8g5bQwlSiGjWw1WRD5vkD BuYMMvHGM1++51Q/VXHGE4jTwiImARw9kMRGKYfz+IcMoZgl2/Y0cvCtqTYKM8nKHqN/Gn iSliXPMBf6MUJ+nfuNxlXXwd8DtNS/E=
To: oauth@ietf.org
References: <7864a74e108141ba9b4a3184c7515d2a@ICTS-S-EXMBX19.luna.kuleuven.be>
From: Daniel Fett <fett@danielfett.de>
Message-ID: <b6a151a7-8d98-eeb1-becc-cec4ca7b06f5@danielfett.de>
Date: Thu, 12 Mar 2020 14:39:30 +0100
MIME-Version: 1.0
In-Reply-To: <7864a74e108141ba9b4a3184c7515d2a@ICTS-S-EXMBX19.luna.kuleuven.be>
Content-Type: multipart/alternative; boundary="------------419E3E49C206C119F086BD9E"
Content-Language: de-DE
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de; s=dkim; t=1584020371; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=8xl8wCt9ETmmtoq6tQRJTRghNLEQKSwQwV2zvcVvnw4=; b=qRaJz0AJzTX5iJXulaDmbUKlfyBS0aXOwCRlV3EEoI4afN3e9uSco4ouDE02dGrQf9VnmB R/oNd77MqFrFaqP1MhsXare8x+fcSGpqvzumZ46TtMKfC7XNs2tWg0WzLPa3v2A9D1FG3B OOprj/z7l1M2pr/2KwVAqkR/nEJfsHs=
ARC-Seal: i=1; s=dkim; d=danielfett.de; t=1584020371; a=rsa-sha256; cv=none; b=s7q3F+b67bjz59P2IztsHKd3MCANhS+Ghg9mal3sIpwz9ztysfTNlGn4LbMafIRcQQzVxwKbNS4Fp5g3AvGR6zbmzwFGqtmbCK5EjvjaOIEi6CUC1vyelTIntzyZap4Nj0Tm9nd2y+7UT5wNYD5sKGZriMYLNX+w18CCl4bf8Ks=
ARC-Authentication-Results: i=1; d3f.me; auth=pass smtp.auth=fett@danielfett.de smtp.mailfrom=fett@danielfett.de
Authentication-Results: d3f.me; auth=pass smtp.auth=fett@danielfett.de smtp.mailfrom=fett@danielfett.de
X-Spamd-Bar: /
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/OVtOUAek9i9u8WX10KjwFvhifw4>
Subject: Re: [OAUTH-WG] Small error in OAuth BCP and new 2.1 draft...
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: Thu, 12 Mar 2020 13:39:35 -0000
Hi Peter,
thanks, this is fixed in the (yet unpublished) version of the Security BCP.
-Daniel
Am 12.03.20 um 14:35 schrieb Pieter Philippaerts:
> Hi everyone,
>
> I hope this is the right mailing list to submit mistakes in the OAuth
> specifications...
>
> I was reading through the latest version of the OAuth 2.0 Security
> Best Current Practice (version 14) and noticed a very small error.
> Section 2.1..1 reads: "To this end, they MUST either (a) publish the
> element "code_challenge_methods_supported" in their AS metadata
> ([RFC8418])...", but the reference to RFC8418 is wrong. RFC8418 is
> totally unrelated to OAuth2 or AS metadata. I believe you wanted to
> link to RFC8414 ("OAuth 2.0 Authorization Server Metadata").
>
> The new OAuth 2.1 draft has the same text (and wrong reference) in
> section 9.7.
>
> Kind regards,
> Pieter
>
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
- [OAUTH-WG] Small error in OAuth BCP and new 2.1 d… Pieter Philippaerts
- Re: [OAUTH-WG] Small error in OAuth BCP and new 2… Daniel Fett