verify CRC checksums

[sadyc]

I have reported this before and I hoped it to be in total commander 6.5:

Why "Verify CRC checksums" from File menu can only be run on files with .md5 or .sfv extensions?
Some Linux distributions or projects use files named md5sum, without any extension.

Please fix this! I can't verify CRCs on linux distribution CDs because of this!

Why force a certain type of extension?
Maybe if extension doesn't match would be proper to display a dialog if the user is sure about what is doing.

--adrian

[djk]

True, Christian has added checking md5sum.txt files but not md5sum (without any extension).

[ghisler(Author)]

I wasn't aware that there is a file called md5sum (without extension). Any other such file names which should be checked?

[Maxwish]

BTW: The commands in the menu are not entirely correct:

"Create CRC Checksums (SFV format)..."
should be
"Create CRC Checksums (SFV, MD5)..."


"Verify CRC Checksums (from SFV files)"
should be
"Verify CRC Checksums (SFV, MD5)"

I know there is an issue with their being a lot of translations of LNG files, but adding the general term "MD5" shouldn't be a problem....

The error message that pops-up when selecting a wrong file for CRC checking (example: readme.txt) show also an incomplete message:
"please select only sfv files!"
should be more like:
"Please only select SFV or MD5 files"

[Maxwish]

FreeBSD checksums are presented in this format:
CHECKSUM.MD5

Code: Select all

MD5 (5.3-RELEASE-i386-bootonly.iso) = e370ae39bb34f0789c638b6ad50038a2
MD5 (5.3-RELEASE-i386-disc1.iso) = fbcbfdff31f27de396f257e0a37a78b8

OpenBSD
MD5 (no extension)

Code: Select all

MD5 (INSTALL.i386) = f95f4f6388c4031871c065b0654d89fc
MD5 (INSTALL.linux) = 34ab7e52e8b1ed96682349a2f0addcce

Debian
md5sum.txt

Code: Select all

0ef7cd5b850818e0d8f830aac60f2430  ./README.txt
dfa33b5bc100cacd35a395d7842f7388  ./READ-ca.txt 

Suse
MD5SUMS (no extension)

Code: Select all

66c9578787b9a49d04e9c64ed95c0785  README.txt
ab648822abbd89906adb66f7cddd6bc2  SUSE-Linux-9.2-FTP-DVD.iso 

REDHAT:
MD5SUM (no extension)

Code: Select all

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

34048ce4cd069b624f6e021ba63ecde5  shrike-i386-disc1.iso
6b8ba42f56b397d536826c78c9679c0a  shrike-i386-disc2.iso
af38ac4316ba20df2dec5f990913396d  shrike-i386-disc3.iso
0727c51ab359dafa9ab31e0c50958aa6  shrike-SRPMS-disc1.iso
2ddd8e6a8502869cd2e78d47590b9be1  shrike-SRPMS-disc2.iso
f378cf68b22c3b9a64c86b5067511630  shrike-SRPMS-disc3.iso
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE/YI35IZGAzdtCpg4RAvKnAKCdjWxxWvRUNOSYrXDVWFZzVG1oTgCcDdQi
Q2ngUUckqHAve4gh8ojUfPU=
=RmmX
-----END PGP SIGNATURE-----

[cHiNgaChg00k]

And it would be cool if it was possible to make some kind of tag inside the dir that says that alle the files have been checked and found ok, or made *.missing fils for those missing and *.bad for files with cr errors (just like som ftp servers have).

[=m4rc=]

Hi
& H4ppY new ye4R

I was wondering if an input field like THIS ONE could be helpfull.
When there is no md5 file coming with your download but the checksum is published on the webpage, how do you verify it ?
(see nero's download pages for exemples)

[ghisler(Author)]

When there is no md5 file coming with your download but the checksum is published on the webpage, how do you verify it ?

Simple:
1. Create SFV file in TC (mode set to MD5)
2. Open .MD5 file with F3
3. Search for the md5 pasted on the web site with F7
-> if it's found, the MD5 is OK.

[=m4rc=]

3. Search for the md5 pasted on the web site with F7
-> if it's found, the MD5 is OK.

hmm, good trick... didn't think about that
until now i only checked visually both sum
merci