-
Notifications
You must be signed in to change notification settings - Fork 15
COVPN-32: Support X25519 x ML-KEM-768 hybrid method #312
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
Conversation
|
Code coverage summary for c2c20f5: ✅ Region coverage 67% passes |
kp-thomas-yau
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For other reviewers: This also includes WolfSSL upgrade to 5.8.2 and WOLFSSL_DTLS_RECORDS_CAN_SPAN_DATAGRAMS.
|
@kp-samuel-tam The issue with WOLFSSL_DTLS_RECORDS_CAN_SPAN_DATAGRAMS has been resolved and wolfssl updated to 5.8.2 version You can rebase on top of latest main branch and remove the unnecessary changes. |
5e5c577 to
3fa58ae
Compare
3fa58ae to
c2c20f5
Compare
Description
Support one additional post-quantum key exchange method, X25519 with ML-KEM-768.
Motivation and Context
The method is drafted in IETF's Post-quantum hybrid ECDHE-MLKEM Key Agreement for TLSv1.3.
How Has This Been Tested?
This PR only changes the server-side groups, to test this effectively we need to change the client's as well.
lightway/lightway-core/src/connection/builders.rs
Line 174 in 7c9eec9
Change this to
X25519MLKEM768. Runningearthly --allow-privileged +e2esucceeds.Related
Types of changes
Checklist:
main