Verify CRC checksums - support for HASHDEEP txt files

[wanderer]

How difficult would it be to add built-in support for HASHDEEP output files when verifying CRC checksums? It seems that all functions already exist in TC (MD5, SHA-1, SHA-256 support), it's just the format of the file that is different.

[ghisler(Author)]

Could you post a sample file created by hashdeep? TC currently supports the de facto hast file standard used on the Internet. Other formats could be added if the format is easy to recognize.

[wanderer]

Here you are:

Code: Select all

%%%% HASHDEEP-1.0
%%%% size,md5,sha1,sha256,filename
542750720,0ea277be0ff3ab92f14f7b9d586d16cd,d3b9ac616995b41b3a578f33d8c76a3519047f02,e0f0ad32b955847d2458c98cf3a303ad5f19576342c8cd7e16fcc801323648bc,wsusoffline-wxp-enu.iso

It contains hashes for several methods in one file. Also md5deep exists in the same site which i suppose has a similar format. I don't have an example for that but if you think it's not that hard to support one of them, maybe it would be easy to support the other as well.

[ghisler(Author)]

So it uses multiple hashes on the same line? Hmm, not very useful. For example, if you already do sha256, sha1 would be just a tiny subset, so it wouldn't make any sense to do both. Any reason for it?

[wanderer]

Any reason for it?

This is used by some tools i've encountered in a couple of cases, which use HASHDEEP to generate checksums. ATM, if one would like to verify the checksum files created by these tools, he would have to create one of the supported kind of checksums from TC (i.e. sha1) and then visually compare them to the one stored in the HASHDEEP txt files. I thought that since TC already supports all those methods, it would be nice if it could recognize this format and verify one of the checksums (the latest probably - i.e. sha256). It's not very important but if it's not that difficult to implement, it would be convenient to have it.

[wanderer]

About this, please note that i'm talking only about verification here, not creation of such files. Just to avoid the current verification process of creating the CRC file and then manually comparing the CRC in the created file to the one in the HASHDEEP txt.

[MVV]

I think we need a simple checksum file parsing API to support any kind of hash files. So, TC may call such plugin and it will return one item per call with file path and hash or hashes to be checked (if they are supported by TC).

[ghisler(Author)]

2MVV
This can already be done with the packer plugin interface. Here is an example of a hash plugin:
http://www.totalcmd.net/plugring/checksum.html

[MVV]

ghisler,
Such kind of plugins would allow using TC hash check dialog with unknown hash files.