MD5 output format problem

[2GKUN4]

I'm using Altap Salamander v2.51 (registered).

The output format of the Plugins->Checksum->Calculate CRC/MD5 Checksums... cannot be verified by a Linux md5sum tool. The problem appears to be a difference in the formatting of the .md5 files.

Altap Salamander output contains lines that look like this:
f0d74f9d1685da0e5f15af64569ed57b test.bin
Note that there is only a single space between the hash and the filename.

The GNU version of md5sum outputs lines that look like this in text read mode:
f0d74f9d1685da0e5f15af64569ed57b test.bin
and like this in binary read mode:
f0d74f9d1685da0e5f15af64569ed57b *test.bin

In the GNU version, the format is:
<128bit checksum><space><binary-flag><filename>
where <binary-flag> is either <space> (text mode default) or * (binary mode -b option).

The MD5 hashes themselves match correctly between the two tools.

[Ether]

I don't understand, where's the problem. Is it the * mark? From what I understand, both file formats are equal, except for the * mark.

[Jan Rysavy]

The problem is in two spaces that md5sum requires. We should probably also insert the * mark.

[Raptor]

So problem is in AS output format or in md5sum output format? Who can tell? Any standards for output files here? GNU doesn't mean standard. Hash is ok, so I don't think there is problem.

[Jan Rysavy]

Our Checksum plugin can read md5sum outpout without problem (variable number of spaces, '*' flag, UNIX end of lines).

Problem is on md5sum side. We will support it in next update of Checksum plugin. There are other requests on this forum (support for more hash functions, non-modal Calculate window, etc).

[2GKUN4]

Thanks.

[Jan Patera]

In the GNU version, the format of MD5 files is:
<128bit checksum><space><binary-flag><filename>
where <binary-flag> is either <space> (text mode default) or * (binary mode -b option).

Since the next version of Altap Salamander (2.52), two spaces will be written between the checksum and filename.