[release/8.0-staging] Permit MD5 regardless of FIPS configuration for Linux#94979
Merged
carlossanlop merged 3 commits intorelease/8.0-stagingfrom Nov 21, 2023
Merged
Conversation
|
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones Issue DetailsBackport of #94934 to release/8.0-staging /cc @vcsjones Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
bartonjs
approved these changes
Nov 20, 2023
Contributor
|
Approved by Tactics via email. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #94934 to release/8.0-staging
/cc @vcsjones @bartonjs
Customer Impact
Customers legitimately using the MD5 algorithm for non-cryptographic purposes get a
CryptographicExceptionon certain Linux configurations; including RHEL (with an opt-in) and Mariner (the new default?).The main known purpose for continuing to use MD5 is to set the Content-MD5 header required on uploading to Azure Blob Storage.
Testing
Verified by running the MD5 tests on a machine in this configuration. CI does not currently have such a configuration.
Risk
Low.
Customers not using MD5 are entirely unaffected. Customers using MD5 on a system without a FIPS lockout are verified by CI. Customers using MD5 on a system with a FIPS lockout are already broken, and have been manually verified as being unbroken.
The affected codepaths are initialization, they do not process arguments, so there are no argument-based edge cases.