To use some hashing tool (like sha1sum
, sha224sum
, sha256sum
, sha384sum
, sha512sum
, md5sum
, shasum
, hashdeep
, etc), a user can't include control fingerprint as a command line argument, he must use file based pairs of filenames with digest or check the match of two strings relying on eye. All mentioned tools work in these 2 ways: provide pairs in the file or check the match yourself.
Is there a reason not to have the command-line argument option?
To be clear, I'd like to have something like that:
$ sha256sum some_important_file ac1847a71b62dc61f5a7164ced8ac2480c42f59652305ef49f4fe62f1fb6be7d some_important_file: OK
or
$ sha256sum some_important_file --fingerprint ac1847a71b62dc61f5a7164ced8ac2480c42f59652305ef49f4fe62f1fb6be7d some_important_file: OK
Can't understand the lack of such a way of use. Seems so useful for controlling just one hash. Any reason not to provide it?
echo "ac1847a71b62dc61f5a7164ced8ac2480c42f59652305ef49f4fe62f1fb6be7d some_important_file" | sha256sum -c -
?you would have to ask the authors of the programs
. Nobody else can answer it.