Upgrade SymCrypt to 103.10.0 and SymCrypt-OpenSSL to 1.9.4#81
Open
securely1g wants to merge 1 commit into
Open
Upgrade SymCrypt to 103.10.0 and SymCrypt-OpenSSL to 1.9.4#81securely1g wants to merge 1 commit into
securely1g wants to merge 1 commit into
Conversation
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
securely1g
force-pushed
the
upgrade-symcrypt-103.10.0
branch
from
be33712 to
c7d2009
Compare
- Update SymCrypt submodule from 103.8.0 (53be637) to 103.10.0 (b39181f) - Update SymCrypt-OpenSSL submodule from 1.7.0 (1bf988b) to 1.9.4 (9fd0228) - Update SYMCRYPT_OPENSSL_VERSION in rules/symcrypt-openssl.mk to 1.9.4 - Update debian/control version to 1.9.4 SymCrypt 103.10.0 adds FIPS integrity verification via pyelftools (already installed by CI via requirements.txt). SymCrypt-OpenSSL 1.9.4 improves the provider interface, which is the preferred integration path for OpenSSL 3.x (engine API is deprecated). Tested on Debian Trixie (OpenSSL 3.5.4): - SymCrypt unit tests pass - symcryptprovider v1.9.4 loads and activates correctly - Verified on SONiC master VS KVM (kernel 6.12.41, Debian 13.3) Signed-off-by: securely1g <securely1g@users.noreply.github.com>
securely1g
force-pushed
the
upgrade-symcrypt-103.10.0
branch
from
c7d2009 to
bcd44a1
Compare
Contributor
|
/azp run |
1 similar comment
Contributor
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
Author
|
@qiluo-msft Could you please review this PR? |
qiluo-msft
approved these changes
Mar 4, 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
3 participants
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.
Changes
Submodule Updates
53be637→b39181f)1bf988b→9fd0228)Version Bumps
rules/symcrypt-openssl.mk:SYMCRYPT_OPENSSL_VERSION1.5.2 → 1.9.4src/SymCrypt-OpenSSL-Debian/debian/control: Version 0.1 → 1.9.4Why
Testing
Tested on Debian Trixie (OpenSSL 3.5.4) with SONiC master VS KVM:
symcryptproviderv1.9.4 loads and activates correctlyBuild Notes
pyelftools==0.29(already installed by CI viasrc/SymCrypt/scripts/requirements.txt)libsymcrypt.sobuild output has execute-only permissions — the packaging Makefile should ensurechmod a+ron installed libraries