While the correctness of the supported hash algorithms can be tested with the built-in self-test feature, these test cases are meant to detect changes in the output format. A follow-up commit will improve the compatibility with the coreutils versions of the hash programs, and these tests should detect any unintended side-effects of such a change on existing functionality.
10 lines
893 B
Plaintext
10 lines
893 B
Plaintext
SHA1 test suite:
|
|
SHA1 ("") = da39a3ee5e6b4b0d3255bfef95601890afd80709 - verified correct
|
|
SHA1 ("a") = 86f7e437faa5a7fce15d1ddcb9eaeaea377667b8 - verified correct
|
|
SHA1 ("abc") = a9993e364706816aba3e25717850c26c9cd0d89d - verified correct
|
|
SHA1 ("message digest") = c12252ceda8be8994d5fa0290a47231c1d16aae3 - verified correct
|
|
SHA1 ("abcdefghijklmnopqrstuvwxyz") = 32d10c7b8cf96570ca04ce37f2a19d84240d3a89 - verified correct
|
|
SHA1 ("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789") = 761c457bf73b14d27e9e9265c46f4b4dda11f940 - verified correct
|
|
SHA1 ("12345678901234567890123456789012345678901234567890123456789012345678901234567890") = 50abf5706a150990a08b2c5ea40fa0e585554732 - verified correct
|
|
SHA1 ("MD5 has not yet (2001-09-03) been broken, but sufficient attacks have been made that its security is in some doubt") = 18eca4333979c4181199b7b4fab8786d16cf2846 - verified correct
|