Skip to content

Clarify Transcript Hash uses messages as sent or received #1407

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
muhammad-usama-sardar wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Clarify Transcript Hash uses messages as sent or received #1407

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
102c228
clarify tx hash
muhammad-usama-sardar Feb 12, 2026
0dee57b
revert changes in first para
muhammad-usama-sardar Feb 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion draft-ietf-tls-rfc8446bis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2995,14 +2995,19 @@ stateless HelloRetryRequest by storing just the hash of ClientHello1
in the cookie, rather than requiring it to export the entire intermediate
hash state (see {{cookie}}).

For concreteness, the transcript hash is always taken from the
Unless specified otherwise, the transcript hash is always taken from the
following sequence of handshake messages, starting at the first
ClientHello and including only those messages that were sent:
ClientHello, HelloRetryRequest, ClientHello, ServerHello,
EncryptedExtensions, server CertificateRequest, server Certificate,
server CertificateVerify, server Finished, EndOfEarlyData, client
Certificate, client CertificateVerify, and client Finished.

Unless specified otherwise, the messages in the transcript hash are
always taken as sent or received by the endpoint without any processing.
This helps to detect any modifications to ensure the integrity of
messages.

In general, implementations can implement the transcript by keeping a
running transcript hash value based on the negotiated hash. Note,
however, that subsequent post-handshake authentications do not include
Expand Down