web: add X25519MLKEM768 post-quantum curve to TLS config#417
Open
Thealisyed wants to merge 1 commit into
Open
Conversation
X25519MLKEM768 is a hybrid post-quantum key exchange combining X25519 with ML-KEM-768. It has been available since Go 1.24 and is enabled by default in TLS 1.3, but users who explicitly set curve_preferences cannot currently include it. Assisted-by: Claude Signed-off-by: Ali Syed <alsyed@redhat.com>
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.
Summary
Add the X25519MLKEM768 hybrid post-quantum key exchange to the supported
curve_preferencesmap inweb-config.yaml.Motivation
X25519MLKEM768 (CurveID 4588) combines X25519 with ML-KEM-768 (FIPS 203). Go 1.24+ includes it in the default TLS 1.3 key exchange preferences when
CurvePreferencesis nil. However, users who explicitly setcurve_preferencesin their web config to control which key exchanges are offered cannot currently includeX25519MLKEM768, which effectively disables post-quantum key exchange for those deployments.This is particularly relevant for projects like Prometheus exporters running in environments with post-quantum cryptography mandates (e.g., OpenShift, which enforces centralized TLS security profiles).
Changes
web/tls_config.go: AddX25519MLKEM768to thecurvesmapweb/testdata/web_config_noAuth_allCurves.good.yml: Add to test fixturedocs/web-configuration.md: Update description to cover non-ECDHE key exchangesNotes
SecP256r1MLKEM768andSecP384r1MLKEM1024. Those can be added in a follow-up when this module bumps its Go version requirement.X25519MLKEM768is TLS 1.3 only. If configured withmin_version: TLS12, Go will silently skip it during TLS 1.2 handshakes — no error, it just won't be negotiated. This is the same behavior as the existing curves.Signed-off-by: Ali Syed alsyed@redhat.com