Cherry-pick #8772 to 6.x: Support parsing TLS 1.3 supported_versions extension (#8647) #8824
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #8772 to 6.x branch. Original message:
This adds support for the new TLS version negotiation mechanism
introduced in TLS 1.3.
It relies on a new extension:
supported_versions
. When thisextension is used in the CLIENT_HELLO message, it features
a list of versions the client is willing to use:
If the server supports the extension, it will pick one of the
offered versions and include it in the SERVER_HELLO message:
The TLS parser will report a new field,
tls.version
, that is theTLS version that has been selected after negotiation, either using
the new negotiation introduced in TLS 1.3 or the legacy negotiation
mechanism that used the version field in HELLO messages.
Update TLS dashboard to use new version field …
tls.server_certificate.public_key_size
Fixes #8647