Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Yes, I'm changing back yet again I've spent some of the last few months working on a project that required extensive investigation into the pros/cons of cryptographic vs. non-cryptographic hashes, collision resistance, and hash size. In short, MD5 remains fine for use for things like unique hashing. FNV is most likely fine, but MD5 is plenty fast for this kind of work. And 32 bits means that a birthday attack/collision becomes much more likely (50% chance of finding one after 77K inputs). SHA1 is overkill, at least for the things we are doing in Horde_Imap_Client.
- Loading branch information
Showing
3 changed files
with
5 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters