Visual RFC.
ALL RFCs / RFC 5246
Read the RFC ↗
RFC 5246 / MECHANISMS

Finished checks the transcript

04

A derived verification value binds the handshake messages to the negotiated secret.

This guide explains the 2008 publication. Superseded by RFC 8446, RFC 9846.

Related RFCs and changes

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

RFC 5246 · § 7.4.9EXAMPLE
3 / 3
Finished checks the transcriptA derived verification value binds the handshake messages to the negotiated secret. Current state: Mismatch stops.Finished checks the transcriptHandshake transcriptClientHello … key exchangemaster secretPRFverify_datamismatchhandshake stopsAn incorrect Finished never opens application traffic.
03
Mismatch stops

An incorrect Finished aborts the handshake rather than opening application traffic.

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

Recipients must verify the Finished contents.

  • Recipients must verify the Finished contents.
  • Finished is the first message protected by the newly negotiated state.
  • Application traffic starts after the required Finished exchange succeeds.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

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

Privacy
All chapters in this RFC
  1. A TLS 1.2 handshake
  2. Pending and current keys
  3. Records protect fragments
  4. Finished checks the transcript
  5. TLS 1.3 changes the design

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗