The following errata report has been verified for RFC8446, "The Transport Layer Security (TLS) Protocol Version 1.3".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8795 -------------------------------------- Status: Verified Type: Technical Reported by: Loïc Ferreira <[email protected]> Date Reported: 2026-03-02 Verified by: Deb Cooley (IESG) Section: 4.6.2 Original Text ------------- A client that receives a CertificateRequest message without having sent the "post_handshake_auth" extension MUST send an "unexpected_message" fatal alert. Corrected Text -------------- A client that receives a CertificateRequest message encrypted with the server_application_traffic_secret_N without having sent the "post_handshake_auth" extension MUST send an "unexpected_message" fatal alert. Notes ----- This sentence is to be understood in the context of a possible post-handshake authentication. During a main handshake, a CertificateRequest message (encrypted with the server_handshake_traffic_secret) may be sent by the server (without need for the client to send a "post_handshake_auth" extension). This has been fixed in 8446bis here: https://github.com/tlswg/tls13-spec/pull/1424 -------------------------------------- RFC8446 (draft-ietf-tls-tls13-28) -------------------------------------- Title : The Transport Layer Security (TLS) Protocol Version 1.3 Publication Date : August 2018 Author(s) : E. Rescorla Category : PROPOSED STANDARD Source : Transport Layer Security Stream : IETF Verifying Party : IESG _______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
