Message173461
| 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 |
<1350837231.92.0.123775563241.issue14621@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|