Command: rhash -MTHC <filename>
Expected Output: <filename> <MD5 Hash> <TTH Hash> <SHA1 Hash> <CRC32 Hash>
Actual Output: <filename> <CRC32 Hash> <MD5 Hash> <SHA1 Hash> <TTH Hash>
It's the first time I've seen any command-line utility display such bizarre non-intuitive behavior, where it completely ignores the argument order specified by the user, and forcibly sticks to its own internally specified order (I think it follows whatever order --list-hashes displays).
Since the Hash Function names are not printed by default (as with similar utilities like FSum), and many Hash Functions have digests of the same length, the default behavior is extremely confusing.
Command:
rhash -MTHC <filename>Expected Output:
<filename> <MD5 Hash> <TTH Hash> <SHA1 Hash> <CRC32 Hash>Actual Output:
<filename> <CRC32 Hash> <MD5 Hash> <SHA1 Hash> <TTH Hash>It's the first time I've seen any command-line utility display such bizarre non-intuitive behavior, where it completely ignores the argument order specified by the user, and forcibly sticks to its own internally specified order (I think it follows whatever order
--list-hashesdisplays).Since the Hash Function names are not printed by default (as with similar utilities like FSum), and many Hash Functions have digests of the same length, the default behavior is extremely confusing.