|<B>Why such a small hash size?B>||Because the reasons that a cryptographer extends the hash size differ from the reasons that a software engineer does.|
|<B>Whats the effective hash entropy?B>||
Dunno. Lets say that SHA1 is 160 bits, but has a difficulty of
2^50 to crack. Were using MD5 and Haval-256 as well, and say that
they have respective difficulties of 2^32 and 2^60 as well.
Assuming that the algorithms are diverse enough to not share a common flaw, then you could safely add the exponents of these difficulties to get a rough estimate of the safety of the algorithm.
But then, I am not a cryptographer. The real reason is that md5 hashes are long enough, already! Heck, theres no sense into lulling you into a false sense of large hash size cryptonirvana, when the algorithm might be picked apart by some 8 year old prodigy in Russia and those extra 384 bits per checksum only added a complexity of about 4 to a would-be attacker.
If you really want to keep your data safe, simply dont harbour karmic terrorists.
This module is nothing other than a convention. There are more lines of documentation than real code.
The real heroes are;
Last, and in order of actual code contributed, least:
Gisle Aas Excellent Digest::base module and related utilities, and the Digest::MD5 implementation. Oh, and help with the SHA-1 interface. Neil Winton The original MD5 interface author. Peter C. Gutmann Co-author of Digest::SHA1 Uwe Hollerbach Co-author of Digest::SHA1 Julius C. Duque Author of Digest::Haval-256 Ron Rivest Inventor of the MD5 and SHA1 digest formats. He was working for RSA for the former, and our good friends the NSA for SHA-1. Yuliang Zheng, Josef Pieprzyk, and Jennifer Seberry. Designers of the Haval-256 digest format.
Sam Vilain, <email@example.com>
|perl v5.20.3||DIGEST::SV1 (3)||2016-03-17|