Skip to content
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.

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

Use handshake bytes more consistently #3775

Merged
merged 1 commit into from Jun 24, 2020
Merged

Conversation

martinthomson
Copy link
Member

This also adds a paragraph about buffering of CRYPTO frames that
references the buffering text in the transport doc.

Closes no issue, but there have been complaints.

This also adds a paragraph about buffering of CRYPTO frames that
references the buffering text in the transport doc.

Closes no issue, but there have been complaints.
@martinthomson martinthomson added editorial An issue that does not affect the design of the protocol; does not require consensus. -tls labels Jun 18, 2020
space.
bytes to be sent, they are appended to the handshake bytes for the current
encryption level. Any packet that includes the CRYPTO frame is protected using
keys from the corresponding encryption level.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not new text, but this feels like it's reversed. It's not the fact that it includes these bytes that causes a packet to use particular keys; the level of these bytes determines which packet type it must be sent in.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#3783 is an attempt to invert this.

@martinthomson martinthomson merged commit d78941f into master Jun 24, 2020
@martinthomson martinthomson deleted the handshake-bytes branch June 24, 2020 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-tls editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants