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

feat: chrome 120 non-pq client hello #268

Merged
merged 1 commit into from
Dec 14, 2023
Merged

feat: chrome 120 non-pq client hello #268

merged 1 commit into from
Dec 14, 2023

Conversation

hax0r31337
Copy link
Contributor

Since Chrome hasn't started enabling TLS 1.3 hybridized Kyber support by default, It's necessary to have an non-PQ ClientHello support in my opinion.

@gaukas
Copy link
Contributor

gaukas commented Dec 14, 2023

Wait, I thought it is enabled? Am I again selected for A/B testing? 🤣

@gaukas
Copy link
Contributor

gaukas commented 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.

@gaukas
Copy link
Contributor

gaukas commented Dec 14, 2023

Thanks @hax0r31337!

@gaukas gaukas merged commit e747779 into refraction-networking:master Dec 14, 2023
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants