From wwwrun@rfcpa.amsl.com  Tue Jan  2 12:04:07 2024
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: pppext@ietfa.amsl.com
Delivered-To: pppext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 021B9C1519B1;
 Tue,  2 Jan 2024 12:04:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level: 
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249,
 RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001,
 SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01,
 URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001]
 autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id OxylJiWu4UWA; Tue,  2 Jan 2024 12:04:03 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256)
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 3007DC1519AE;
 Tue,  2 Jan 2024 12:04:03 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499)
 id D92455C05BA; Tue,  2 Jan 2024 12:04:02 -0800 (PST)
To: christophe.deleuze@free.fr,  glennz@microsoft.com, stevec@microsoft.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: rfc-ed@rfc-editor.org, iesg@ietf.org, pppext@ietf.org, iana@iana.org,
 rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20240102200402.D92455C05BA@rfcpa.amsl.com>
Date: Tue,  2 Jan 2024 12:04:02 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pppext/4yqxr_uEgG7w1vhyl2MFzYhjRQU>
Subject: [Pppext] [Errata Verified] RFC2433 (7742)
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pppext>,
 <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pppext/>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>,
 <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2024 20:04:07 -0000

The following errata report has been verified for RFC2433,
"Microsoft PPP CHAP Extensions". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7742

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Christophe Deleuze <christophe.deleuze@free.fr>
Date Reported: 2023-12-28
Verified by: RFC Editor  

IESG Note

Original Text
-------------
The protocol described here has significant vulnerabilities.  People
planning on implementing or using this protocol should read section
12, "Security Considerations".

Corrected Text
--------------
The protocol described here has significant vulnerabilities.  People
planning on implementing or using this protocol should read section
11, "Security Considerations".

Notes
-----
The section number is incorrect.


--------------------------------------
RFC2433 (no draft string recorded)
--------------------------------------
Title               : Microsoft PPP CHAP Extensions
Publication Date    : October 1998
Author(s)           : G. Zorn, S. Cobb
Category            : INFORMATIONAL
Source              : Point-to-Point Protocol Extensions
Area                : Internet
Stream              : IETF