Disable FIPS cryptographic exceptions#702
Merged
KirillOsenkov merged 1 commit intoKirillOsenkov:mainfrom Aug 28, 2023
Merged
Conversation
cd856d4 to
eb8acf5
Compare
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
2 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.
In .NET Framework 4.7.2 and earlier versions, managed cryptographic provider classes such as System.Security.Cryptography.MD5 throw a System.Security.Cryptography.CryptographicException when the system cryptographic libraries are configured in FIPS mode.
The issue is encountered in the log viewer when needing to write content to a temporary file path e.g. when preprocessing a project node to view the full project XML.
The fix taken here to to turn off the exception throwing behavior via an app runtime switch.
Closes: #701