I mentioned md5sum a long, long time ago, and now I feel obligated to include the sha* suite. I think this might be where the free ride ends for checksum generators though. Here’s why:
That’s it, that’s basically all it does. Of course, it’s not like md5sum did much more. You can use this in much the same way as md5sum — checking file integrity where the publisher has a sum available to match, or as a fingerprinting utility where there was an intermediary in the transfer.
I can’t speak for either of those last programs, since I’m not sure what their original intent was. I have a feeling
sha1pass works with passwords and encryption, while
shasum appears to be a frontend for the sha* binaries. If you use sha* enough,
shasum might be helpful.
But that’s why I said the gravy train might be pulling into the station for checksum generators: They have a very slim and specific function. And what I’ve seen of a few other checksum generators suggests that’s all they’re meant to do.