Enhance SHA256GEN.ps1 to include manifest generation - #1
Open
zaxlofful wants to merge 7 commits into
Open
Conversation
I really liked your script and it was exactly what I needed, but I realized that there was one issue. The SHA256 file was getting hashed as it was created. Which is not workable. With this change, it will get a hash that can survive folder movement. Updated the script to generate a SHA-256 manifest and compute a master hash from the file hashes. Got the idea from: https://stackoverflow.com/questions/64467425/md5-checksum-hashing-with-powershell-for-a-whole-directory
Refactor SHA256 verification script to improve error handling and manifest validation.
Author
|
I made it so the check file would account for the master hash |
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
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.
I really liked your script and it was exactly what I needed, but I realized that there was one issue. The SHA256 file was getting hashed as it was created. Which is not workable.
With this change, it will get a hash that can survive folder movement.
Updated the script to generate a SHA-256 manifest and compute a master hash from the file hashes.
Got the idea from: https://stackoverflow.com/questions/64467425/md5-checksum-hashing-with-powershell-for-a-whole-directory