Recent Posts

1

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by Mathias (Author) on Today at 12:40:09 »

Use-case for text mode
A text file is created in linux. and that file is open on Windows, in an OLD editor so when file is saved (without any changed) it replaces LF with CRLF,  the checksum would still be the same. even if filesize is different and the file content has changed.

Now If you create a file in text mode on linux and compare it on Windows in Binary mode.. they will match.  Only the above very narrow use case will fail.

2

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by Mathias (Author) on Today at 12:18:38 »

No it is not a hack. It is an unsupported mode that nobody uses. There is no official spec.

Text mode will not be supported, (Require to much work for something that nobody uses) , it is too weird of a use-case, to much can go wrong.  I never seen anyone support it,  You have checksum to check if file is valid and not changed. Then you want a checksum of entire file. not only some parts of it.

3

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by SwissKnife64 on Today at 12:03:01 »

To ignore the format marker for SHA checksum is a HACK, that will work in most cases, but not in all.

SHA1 file can be generated in text or binary mode, and on Linux the default is text!

Command in Linux for text mode: sha1sum -t filename.sha1, the resulting checksum file has "  " as format marker in front of the file name
Command in Linux for binary mode: sha1sum -b filename.ext, the resulting checksum file has " *" as format marker in front of the file name
Without an option, text mode is used

So only reading the marker and calling the calculation in the correct mode is the 100% solution.

4

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by Mathias (Author) on Today at 11:44:37 »

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..

5

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by SwissKnife64 on Today at 11:42:31 »

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.

6

Support and Feedback / Re: File Verifier start of calculation

« Last post by Mathias (Author) on Today at 11:40:53 »

I don't like autostart because it does not work for the way I use it. I like adding files to check (large ones),  and then I add some more, and then some more.. and then I start the work and can leave the machine to work and go to something else.

Checksum module currently don't do any settings/customizations. Not sure I want to add a whole settings things for just one settings . Hmm I see if I can add add settings for it someway or something.

7

Support and Feedback / Re: File Verifier tab column header

« Last post by Mathias (Author) on Today at 11:34:33 »

column should not be able to be reordered.  I will fix that

8

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by Mathias (Author) on Today at 11:30:45 »

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.

9

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by SwissKnife64 on Today at 11:16:54 »

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.

10

Support and Feedback / Re: File Verifier does NOT check sha files

« Last post by Mathias (Author) on Today at 11:08:17 »

Not sure what you mean with binary.  all checksum files are text files.