Update SymCrypt-OpenSSL to 1.10 with ML-KEM support#17967
Open
mamckee wants to merge 1 commit into
Open
Conversation
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
microsoft-github-policy-service
Bot
added
Packaging
3.0-dev
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
SymCrypt-OpenSSL 1.10 was created as a special release to backport ML-KEM into the stable 1.9 version that's currently available on AZL3. The backport isolated changes to the new ML-KEM and ML-KEM hybrid algorithms to avoid regressions to existing algorithms. Changes can be found here: microsoft/SymCrypt-OpenSSL#171
This PR bumps the SymCrypt-OpenSSL package to 1.10 with ML-KEM and ML-KEM hybrid support. No changes to SymCrypt are required.
Testing
The changes were tested in the SymCrypt-OpenSSL build CI/CD pipeline, which includes OpensSSL EVP tests, and integration tests. The changes were validated against the relevant test suites for the AZL3 versions of CURL, .NET runtime 8/9, golang, nginx, NodeJs, perl, and rust-openssl.
The changes were built into a preview package and deployed to PPE. Confirmed no regressions and little to no overhead to TLS connections when using the new ML-KEM key exchange groups.