[http-auth] [Technical Errata Reported] RFC7804 (5496)
RFC Errata System <rfc-editor@rfc-editor.org> Sat, 08 September 2018 13:51 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3BBF124BE5 for <http-auth@ietfa.amsl.com>; Sat, 8 Sep 2018 06:51:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 joNCtdoVciEK for <http-auth@ietfa.amsl.com>; Sat, 8 Sep 2018 06:51:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 029E8128766 for <http-auth@ietf.org>; Sat, 8 Sep 2018 06:51:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 08ECDB82672; Sat, 8 Sep 2018 06:51:46 -0700 (PDT)
To: alexey.melnikov@isode.com, kaduk@mit.edu, ekr@rtfm.com, ynir.ietf@gmail.com, rifaat.ietf@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: poccil14@gmail.com, http-auth@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180908135146.08ECDB82672@rfc-editor.org>
Date: Sat, 08 Sep 2018 06:51:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/http-auth/jECYn5nEftca3Sp_DaDI84ey4rU>
Subject: [http-auth] [Technical Errata Reported] RFC7804 (5496)
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: HTTP authentication methods <http-auth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-auth>, <mailto:http-auth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-auth/>
List-Post: <mailto:http-auth@ietf.org>
List-Help: <mailto:http-auth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-auth>, <mailto:http-auth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Sep 2018 13:51:49 -0000
The following errata report has been submitted for RFC7804, "Salted Challenge Response HTTP Authentication Mechanism". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5496 -------------------------------------- Type: Technical Reported by: Peter Occil <poccil14@gmail.com> Section: 2.2 Original Text ------------- o Normalize(str): Apply the Preparation and Enforcement steps according to the OpaqueString profile (see [RFC7613]) to a UTF-8 [RFC3629] encoded "str". The resulting string is also in UTF-8. Note that implementations MUST either implement OpaqueString profile operations from [RFC7613] or disallow the use of non US-ASCII Unicode codepoints in "str". The latter is a particular case of compliance with [RFC7613]. Corrected Text -------------- o Normalize(str): Apply the Preparation and Enforcement steps according to the OpaqueString profile (see [RFC7613]) to a UTF-8 [RFC3629] encoded "str". The resulting string is also in UTF-8. Note that implementations MUST either implement OpaqueString profile operations from [RFC7613] or disallow the use of Unicode codepoints not ranging from U+0020 to U+007E in "str". The latter is a particular case of compliance with [RFC7613]. Notes ----- Control code points (including the ASCII controls U+0000 to U+001F as well as U+007F) are disallowed in the PRECIS FreeformClass, which the OpaqueString profile uses. Thus it's not enough to just disallow non-US-ASCII codepoints (rather than implement the full OpaqueString profile) to comply with a subset of the OpaqueString profile. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7804 (draft-ietf-httpauth-scram-auth-15) -------------------------------------- Title : Salted Challenge Response HTTP Authentication Mechanism Publication Date : March 2016 Author(s) : A. Melnikov Category : EXPERIMENTAL Source : Hypertext Transfer Protocol Authentication Area : Security Stream : IETF Verifying Party : IESG
- [http-auth] [Technical Errata Reported] RFC7804 (… RFC Errata System
- Re: [http-auth] [Technical Errata Reported] RFC78… Benjamin Kaduk
- Re: [http-auth] [Technical Errata Reported] RFC78… Alexey Melnikov
- Re: [http-auth] [Technical Errata Reported] RFC78… Benjamin Kaduk