Add FIPS SHA3-256 and complete selected-file CSV/XLSX reports - #44
Open
bellabaelfire wants to merge 2 commits into
Open
Add FIPS SHA3-256 and complete selected-file CSV/XLSX reports#44bellabaelfire wants to merge 2 commits into
bellabaelfire wants to merge 2 commits into
Conversation
Author
|
/claim #2 |
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
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.
Adds SHA3-256 to the evidence table, System Console, and all report paths for #2. Selected PDF/JPG/other evidence files can now be exported to Hash CSV and a genuine
.xlsxworkbook; the existing Email CSV remains available. PDF, DOCX and email PDF include the same SHA3-256 digest. Exports reject pending or failed hashes, and a read failure no longer strands later files in the queue.Because the issue explicitly calls for FIPS 202, this uses pinned MIT
js-sha3rather thanCryptoJS.SHA3: CryptoJS documents its Keccak naming mismatch, and js-sha3 exposes SHA3 and Keccak separately. Existing MD5/SHA-256 stay on CryptoJS. Pinned SheetJS CE generates actual XLSX files; the vendored libraries include licenses. Whole-file/main-thread processing remains an inherited limitation.Validation on Windows, Node 24.19.0 and headless Microsoft Edge:
git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --check, preserving the original CRLF HTML file.Reproduction commands and limitations are in
TESTING.md.Resolves #2.
/claim #2
Bounty listing: https://algora.io/amithmandassociates-oss/hash-report-tool/issues/2