Skip to content

Clarify that extensions can modify the message sequence #1402

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
davidben wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify that extensions can modify the message sequence #1402

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 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 @@ -1283,7 +1283,8 @@ processed and transmitted as specified by the current active connection state.
} Handshake;

Protocol messages MUST be sent in the order defined in
{{the-transcript-hash}} and shown in the diagrams in {{protocol-overview}}.
{{the-transcript-hash}} and shown in the diagrams in {{protocol-overview}},
unless modified by a TLS extension.
A peer which receives a handshake message in an unexpected order
MUST abort the handshake with an "unexpected_message" alert.

Expand Down