#2 Wrong MD5 Calculated.

[0rkaM]

I downloaded the XP Special tables and relative md5 file from https://sourceforge.net/projects/ophcrack/files/tables/XP%20special/ and when I verified with CheckSumControl every file except the .index appeared as incorrect... also when I created the md5 file with CheckSumControl all except the .index files appeared with a different md5sum.
Attached are the original md5 file, the one created with CheckSumControl, and various from other programs with similar functionality.
To reproduce, just verify against any other file then the ones ending by .index from the above link.

[Reinhard Berger]

I can not verify this.
1.) the file "md5sum.txt" uses 2 spaces after the checksum, which leads to a wrong filename e.g. filename should be "table3.bin" but it is " table3.bin" (it contains a space sign before the filename).
2.) This can lead to a "missing file" since filenames with spaces in the beginning are not allowed.
3.When i compare the checksums i can not find a "wrong" calculated one.
E.g.
Checksum from md5sum.txt for file "table3.bin"
f56973caa24e1a87894ed4e78d2a3160
Checksum calculated from checksumcontrol :
F56973CAA24E1A87894ED4E78D2A3160
the only difference is , that it is stored uppercase.
I added a new fixed version that cuts the space sign from the filename, so you should be able to verify the files against the md5sum.txt file.

Also take a look to the screenshot, it shows both checksums and displays the files as ok.