Visual RFC.
ALL RFCs / RFC 8446
Read the RFC ↗
RFC 8446 / AUTHENTICATION

Authentication and failure

06

Certificate checks, proof of key possession, and transcript authentication answer different questions.

This guide explains the 2018 publication. Superseded by RFC 9846.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 4.4 ↗
RFC 8446 · § 4.4EXAMPLE
4 / 4
Authentication and failureA certificate document feeds distinct identity, private-key, and transcript checks; failed verification ends in an alert.Three checks, one authenticated handshakeCertificate✓Credentialtrusted identity×CertificateVerifyprivate-key proof–Finishedtranscript integrityfailure → alertconnection terminates
04
Stop on failed verification.

A failed CertificateVerify produces decrypt_error; do not proceed as authenticated.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

A valid chain does not replace the rest of authentication.

  • CertificateVerify signs a context-bound transcript hash.
  • Finished verifies the handshake transcript using a derived key.
  • Fatal errors close the connection; close_notify signals an orderly end of one sending direction.
DETAILS

The examples simplify the wire representation. Follow the linked specification and application profile for implementation.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. The encrypted handshake
  2. Separate keys for separate jobs
  3. Inside an encrypted record
  4. Resume with a ticket
  5. Early data can be replayed
  6. Authentication and failure
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗