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
820 B
Plaintext
10 lines
820 B
Plaintext
MD5 test suite:
|
|
MD5 ("") = d41d8cd98f00b204e9800998ecf8427e - verified correct
|
|
MD5 ("a") = 0cc175b9c0f1b6a831c399e269772661 - verified correct
|
|
MD5 ("abc") = 900150983cd24fb0d6963f7d28e17f72 - verified correct
|
|
MD5 ("message digest") = f96b697d7cb7938d525a2f31aaf161d0 - verified correct
|
|
MD5 ("abcdefghijklmnopqrstuvwxyz") = c3fcd3d76192e4007dfb496cca67e13b - verified correct
|
|
MD5 ("ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789") = d174ab98d277d9f5a5611c2c9f419d9f - verified correct
|
|
MD5 ("12345678901234567890123456789012345678901234567890123456789012345678901234567890") = 57edf4a22be3c955ac49da2e2107b67a - verified correct
|
|
MD5 ("MD5 has not yet (2001-09-03) been broken, but sufficient attacks have been made that its security is in some doubt") = b50663f41d44d92171cb9976bc118538 - verified correct
|