md5sum: md5sum is … md5sum

I have to include m5sum in this little venture, not because it has a rabid fan base, but because … well, because md5sum is md5sum.


To the best of my knowledge, that’s all it does. It does have a few flags that are available, but nothing that seems to deviate wildly from what you see above.

For my own part I generally only use md5sum when I need to verify that files were transferred correctly. This could be a download, which is what most people probably use md5sum for.

But I have also fallen back to md5sum in the past, to check that files were copied accurately.

It’s probably not the best tool for that job (I think there are some specific tools to check for errors in transfer) but it’s usually quick and correct. And easy to spot a difference without needing to skim through every line of a file.

I have heard of people using md5sum as a kind of fingerprinting tool in the same way, to see if a file was retouched by an intermediary.

If I remember right, in that case someone had uploaded a file to a hosting service, and another person downloaded it, then checked the md5sums on both sides to see if the host had watermarked or tampered with the contents.

Right or wrong, I think it led to the conclusion that the host was adding to exif data at some point. My memory is a little foggy here; this was from years back.

The point of all this is, md5sum may not look like much, but like so many tools it all depends on how you put it to use. 😉

P.S.: Another jewel from coreutils.

2 thoughts on “md5sum: md5sum is … md5sum

  1. Pingback: sha* (with sha1pass and shasum): Sha-sha-sha | Inconsolation

  2. Pingback: Bonus: A massive missive of omission | Inconsolation

Comments are closed.