feat: enable ML-KEM post-quantum TLS key exchange for AL2023 nginx#145
Open
palmep wants to merge 1 commit into
Open
feat: enable ML-KEM post-quantum TLS key exchange for AL2023 nginx#145palmep wants to merge 1 commit into
palmep wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description of changes: The latest AL2023 AMI includes OpenSSL 3.5, allowing for ML-KEM hybrid post-quantum key exchange without any custom compilation.
This change enables TLS 1.3 (alongside TLS 1.2) and configures the nginx
ssl_conf_command Groupsdirective to offerX25519MLKEM768as the preferred key exchange group, with classicalx25519andsecp256r1as fallbacks for clients that don't yet support PQC.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.