This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients Arfrever, PaulMcMillan, Vlado.Boza, arigo, benjamin.peterson, christian.heimes, dmalcolm, koniiiik, vstinner
Date 2012-10-21.16:33:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As far as my understanding goes the issue can't be solved with our current hash algorithm. We'd have to use a crypto hash function or at least a hash algorithm that has an increased avalanche effect on the outcome. The current hash algorithm is designed and optimized for speed and not for security. Any other algorithm is going to slow down hashing.

Small strings and strings with lots of NUL bytes may leak too many information, too.
Date User Action Args
2012-10-21 16:33:51christian.heimessetrecipients: + christian.heimes, arigo, vstinner, benjamin.peterson, Arfrever, dmalcolm, PaulMcMillan, Vlado.Boza, koniiiik
2012-10-21 16:33:51christian.heimessetmessageid: <>
2012-10-21 16:33:51christian.heimeslinkissue14621 messages
2012-10-21 16:33:51christian.heimescreate