The correctly formatted md5sum file

Report problems you've encountered using hkSFV.

Moderators: Big-O Ryan, Big-O Mark

Post Reply
md5sum user

The correctly formatted md5sum file

Post by md5sum user »

I just saw a md5 file created with your tool. My first thought was wtf?
A small hint, the original tools are the 'md5' tool and the other one 'md5sum'.

The output of your hksfv looks like the md5sum one:
- 32 characters representing the md5 value
- a space
- either a '*' or a ' ' to indicate binary or text mode
- and finally the filename ending with a '\n'

but there is a real bug and a compatibility issue with the files generated with your tool:
- bug: the comment character marking a line as comment is '#' and not ';'
- issue: the output file should be in unix file format, as the original unix md5sum treats the \r as part of the filename (and fails to find the file).
to increase compatibility please always output the file in unix format.

and yes, the filename can contain dir names and spaces, it's no problem to have lines like:
0123456789abcdef0123456789abcdef *some dir/test/file.txt

the windows build even smb share names like:
0123456789abcdef0123456789abcdef *//sharename/dir/filename

the other standard is the one created by the original md5 reference implementation (made by rsa who btw created md5):
MD5 (filename) = 0123456789abcdef0123456789abcdef

that's it.
Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests