-
Notifications
You must be signed in to change notification settings - Fork 8
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
Right-to-left parsing #90
Comments
treiher
pushed a commit
that referenced
this issue
Oct 5, 2022
treiher
pushed a commit
that referenced
this issue
Oct 5, 2022
Calculate TLS_Heartbeat message with TLS_Plaintext_Length as defined in rfc6520. ref #90
treiher
pushed a commit
that referenced
this issue
Oct 6, 2022
treiher
pushed a commit
that referenced
this issue
Oct 6, 2022
Calculate TLS_Heartbeat message with TLS_Plaintext_Length as defined in rfc6520. ref #90
treiher
pushed a commit
that referenced
this issue
Oct 6, 2022
treiher
pushed a commit
that referenced
this issue
Oct 6, 2022
Calculate TLS_Heartbeat message with TLS_Plaintext_Length as defined in rfc6520. ref #90
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One TLS 1.3 message needs to be parsed from right to left. An optional and variable number of zero bytes must be read until a marker (
Content_Type
) is found. All bytes left to the marker represent the content of the message.We think the fields should be specified in the order in that the fields will be parsed (i.e. in reversed order of the actual message format):
The shown example also depends on #61 and #62.
The text was updated successfully, but these errors were encountered: