feat: chrome 120 non-pq client hello #268
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Wait, I thought it is enabled? Am I again selected for A/B testing? 🤣 |
gaukas
approved these changes
Dec 14, 2023
|
According to chromestatus.com(https://chromestatus.com/feature/5257822742249472), it is being shipped not in Chrome 120 but only starting Chrome 121. Then well I guess all my machines are selected for the A/B testing. Fair. |
|
Thanks @hax0r31337! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since Chrome hasn't started enabling
TLS 1.3 hybridized Kyber supportby default, It's necessary to have an non-PQ ClientHello support in my opinion.