MD5/SHA1 checksum verify - file extension error

[davop]

Not all md5 / sha1 checksum files that can be downloaded from the Internet are conforming to the same naming / extension format (*.md5, *.sha / *.sha1).

One example I ran into today is an ISO image for a Linux distribution where the extension was *.ms5sum
Selecting Files -> Verify checksum in this case resulted in error message
---------------------------
Total Commander
---------------------------
Please select only SFV, MD5 or SHA files!
---------------------------
OK
---------------------------

Since this is obviously md5 checksum file which TC does not recognize as such due to it failing file extension test, perhaps it would be possible to either:
a) extend allowed extension list to handle more cases,
b) find smarter way to verify if a file indeed contains checksums, or
c) always assume file under selection is a checksum file if user initiates checksum check.

Extensions I have come across that are not supported include:

*.sha1sum
*.sha1sums
*.md5sum
*.md5sums
md5sums (only filename without extension, athough "md5sum" works )

Perhaps a good test for case a) above, would be if either extension or filename start with sha1* or md5* ?

[ghisler(Author)]

TC only checks the extension at this time, not the contents. I will consider to support the above extensions too.

[davop]

Great - thanks.

I also ran into another unsupported case today:

md5sum.txt
sha1sum.txt

[kesdoputr]

Is it possible to make the checksum's content to be UPCASE?It's usually seen in checksum files.

[fenix_productions]

@ghisler(Author)

TC only checks the extension at this time, not the contents. I will consider to support the above extensions too.

Wouldn't it be better to make it configurable by INI parameter?

[ghisler(Author)]

Maybe, but only additionally...

[white]

Why does Total Commander check the file name extension? I have noticed Total Commander auto detects the kind of checksum for each line. So you can mix all kinds of checksums in one file and verify them in one go with Total Commander. Why do you have to name such file for example "md5sums" in order to be able to verify the file?

Moreover using Total Commander you can create checksums files with any name. The file name extensions ".sfv", ".md5", ".sha" are suggestions only. But you can't verify those files with Total Commander without renaming them first.

Why not give the user the choice to continue when Total Commander does not recognize a file as a checksums file?

[ghisler(Author)]

TC does this to prevent users from selecting the files to be checked themselves instead of the associated checksum files.

[white]

TC does this to prevent users from selecting the files to be checked themselves instead of the associated checksum files.

So you could warn the user about that and give him the choice to continue anyway. For example like this:

Some files do not seem to be SFV, MD5, SHA files.
Continue anyway?

OK, Cancel

[lizy11]

Hey guys,
I'm looking for a way to get MD5 and SHA1 Hash code of a file in Windows 7 x64.
Any helps would be appreciate.

Thanks

[white]

I'm looking for a way to get MD5 and SHA1 Hash code of a file in Windows 7 x64.
Any helps would be appreciate.

Check out menu option Files/Create Checksum File(s) (CRC32,MD5,SHA1).