Multi Commander > Support and Feedback

File Verifier does NOT check sha files

<< < (2/3) > >>

Mathias (Author):
Not sure what you mean with binary.  all checksum files are text files.

SwissKnife64:
When calculating the check sum, the input file normally is read "byte by byte", what is called "binary" mode of calculation. This is why in the checksum file, the * in front of the file name marks the calculation as binary.
Alternatively, the input is read as text, transforming line breaks to the system settings, what is called "text" mode of calculation. This is why in the checksum file, the second " " in front of the file name marks the calculation as text.

Mathias (Author):
When getting checksum of a file, the data from the file is always read as binary. they are never converted into text.   to much can go wrong with that.

SwissKnife64:
Please read all my comments carefully. I am not a random support forum poster. I report real problems.

When generating a SHA1 file, reading the input byte by byte, the correct .SHA1 file has a * in front of the file name: E836D9DCBE84E119124034499EBC62DE183C35B6 *LoreIpsum.txt

Your "File Verifier" for .SHA1 tries to open the file "*LoreIpsum.txt" (with the * in the file name) and the verification fails because the file is not found.

Mathias (Author):
I never seen * in sha files.. But I make sure it strips them if they are there
and all all space and * between checksum and filename in the file, so it will work with 1 ,2,3,or 100 spaces..

Navigation

[0] Message Index

[#] Next page

[*] Previous page