Addendum Fix to support FIPS enabled machines with MD5 hashing #17043
+4
−2
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.
Complete FIPS compliance fixes for MD5 hashing
This PR completes the work started in the previous merge (#15299), which addressed the issue of FIPS-enabled machines prohibiting MD5 hashing. The previous PR used the
usedforsecurity=False
flag with hashlib.md5() to resolve the issue, but it missed applying this change in a few locations within the codebase. The following changes ensure full compliance with FIPS requirements across the entire library.FIX #17031