evergreen: y2030 - stop producing SHA1 and MD5 files, and only provide SHA256 files #1625
Conversation
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
…e SHA256 files To comply with complete withdrawal of SHA1 usage by both IETF RFC (non-fips) and NIST CMPV (fips) by 2030, stop producing SHA1 and MD5 checksum files in favor of only providing SHA256 checksum files. As we enter 2026, software produced today might be in active use in 2030 hence it is best to be forward looking with this. If anything breaks, this can be reverted with a migration plan figured out to be executed by 2030.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
To comply with complete withdrawal of SHA1 usage by both IETF RFC
(non-fips) and NIST CMPV (fips) by 2030, stop producing SHA1 and MD5
checksum files in favor of only providing SHA256 checksum files.
As we enter 2026, software produced today might be in active use in
2030 hence it is best to be forward looking with this.
If anything breaks, this can be reverted with a migration plan figured
out to be executed by 2030.