feat: add backwards compatible hybrid PQ policies - #6044
Merged
Conversation
jouho
approved these changes
Aug 19, 2026
alexw91
approved these changes
Aug 20, 2026
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
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.
Goal
Create backwards compatible hybrid ML-KEM policies to support PQ upgrade
Why
Users on these policies need a path to migrate to PQ:
CloudFront-TLS-1-2-2021,20200207, and20230317.How
Replace
kem_preferences_nullin the base policies withkem_preferences_pq_tls_1_3_ietf_2025_07that supports 3 hybrid ML-KEM groups.Callouts
20200207supports only TLS 1.3 ciphers despiteminimum_protocol_versionbeingS2N_SSLv3, which I assume is for compatibility concerns. I added it to the exception list in the PQ policies test.Testing
Existing CI should pass.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.