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.

Sign up for GitHub

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

Jump to bottom

tls: Add a flag to use ML-KEM instead of Kyber #1112

Merged
merged 2 commits into from
Oct 7, 2024
Merged

tls: Add a flag to use ML-KEM instead of Kyber #1112

merged 2 commits into from
Oct 7, 2024

Commits on Oct 7, 2024

  1. tls: Add a flag to use ML-KEM instead of Kyber 

    The flag is disabled by default for now. We'll enable it by default
after server early adopters have had time to deploy the new codepoint.

ML-KEM and Kyber are very similar, so the compatibility and
performance risks between the two are expected to be identical.
Thus, to minimize interruption to enterprise administrators,
ML-KEM is still gated on the same flags as Kyber was. The new flag
changes the meaning of the old flags to gate Kyber instead.

See https://chromium-review.googlesource.com/c/chromium/src/+/5823718
and https://boringssl-review.googlesource.com/c/boringssl/+/70547.

Related to #935.
    @Chilledheart
    Chilledheart committed Oct 7, 2024
    Configuration menu
    Copy the full SHA
    24ef7b4 View commit details
    Browse the repository at this point in the history

  2. tls: support post quantumn key-agreements in server side

    @Chilledheart
    Chilledheart committed Oct 7, 2024
    Configuration menu
    Copy the full SHA
    de83d0b View commit details
    Browse the repository at this point in the history