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 dstufft
Recipients dstufft, rhettinger
Date 2015-03-19.23:01:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426806100.55.0.69770374717.issue23712@psf.upfronthosting.co.za>
In-reply-to
Content
To be clear, I have no opinion on your specific proposal and I don't know if the difference between "cryptographically secure" and "not cryptographically secure" matters for it. I just wanted to be clear that with SipHash an attacker should *not* be able to choose keys that will collide on purpose, but given the small output space (64bits IIRC) that collisions are more likely to occur than with MD5, SHA1, SHA2, etc.
History
Date User Action Args
2015-03-19 23:01:40dstufftsetrecipients: + dstufft, rhettinger
2015-03-19 23:01:40dstufftsetmessageid: <1426806100.55.0.69770374717.issue23712@psf.upfronthosting.co.za>
2015-03-19 23:01:40dstufftlinkissue23712 messages
2015-03-19 23:01:40dstufftcreate