Three formats
hash name from sha256sum/md5sum, SHA256 (name) = hash from macOS and openssl, and the Get-FileHash PowerShell table, header included.
Integrity
Checksum files
A checksum file lists the hashes of several files: it travels with the data and lets anyone verify that nothing changed. The module verifies them in batch and creates them from files and folders. It reads the formats you actually meet — the sha256sum one, the macOS one and the PowerShell table — in any encoding, and when a line does not match it says why.
What it does
What the Checksum files module does
Any encoding
UTF-8, UTF-16 (what PowerShell 5 writes) and Windows-1252 for accented names written by Windows programs. The report states which encoding the file was read with.
Diagnoses that explain
A path truncated by PowerShell with “...” is recognised as such, with the command to regenerate the file; a checksum file listing itself is explained; a file chosen by mistake is called “not a checksum file”.
Create from files and folders
Add files or whole folders, also by dragging them, choose the algorithm and save a file that can be verified with Probatio or with sha256sum -c.
PDF report
File by file: matches, does not match, missing, with the recognised algorithm.
Step by step
How it works
- Verify: open or drop the checksum file; the listed files are looked up in its folder.
- Create: add files and folders, choose the algorithm, save.
FAQ
Frequently asked questions
Why doesn't a PowerShell checksum file verify with sha256sum?
PowerShell 5 writes UTF-16 in table form, and may truncate long paths with “...”. Probatio reads that form, recognises truncated paths and suggests the command to regenerate the file.
Where are the listed files looked up?
In the checksum file's folder, like
sha256sum -c.
Related modules