Change: Use sha256sum instead of md5 for checks #1056
Merged
Conversation
This file contains 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
ArnoStiefvater
previously approved these changes
Mar 17, 2022
ArnoStiefvater
force-pushed
the
replace-md5-with-sha256
branch
from
376249c
to
0a58f20
Compare
y0urself
approved these changes
Mar 17, 2022
nichtsfrei
approved these changes
Mar 17, 2022
nichtsfrei
force-pushed
the
replace-md5-with-sha256
branch
from
0a58f20
to
7492ced
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What:
Use sha256sum instead of md5 for checks
SC-557
Why:
Improvement. This change deprecates the usage of the feed's md5sums and md5sums.asc files, which reduces the feed size and reduces the work necessary for the feed deployment (not having to create the md5sums file and its signature file)
How:
greenbone-nvt-sync --selftest
Checklist: