Use SHA256 for RPM digest#14269
Merged
NikolaMilosavljevic merged 1 commit intodotnet:mainfrom Dec 8, 2023
Merged
Conversation
jkoritzinsky
approved these changes
Dec 8, 2023
This was referenced Dec 8, 2023
This was referenced Jan 4, 2024
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.
Fixes: dotnet/runtime#95759
FIPS compliance blocks installation of RPM packages that use MD5 digest algorithm. We use
fpmtool which defaults to MD5 digests. The fix is to specify SHA256 instead.This is the same fix that was made by many other RPM package owners, for instance: https://github.com/influxdata/telegraf
Similar fixes are needed in
aspnetcoreandinstallerrepos.