➜

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 vstinner
Recipients antoine.pietri, christian.heimes, loewis, vstinner
Date 2018-10-10.21:27:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1539206874.99.0.788709270274.issue34930@psf.upfronthosting.co.za>
In-reply-to
Content 
I dislike modifying a hash function to return its output but keep the same name. For name, "SHA1" must remain "SHA1". If you want a variant, it should have a different name, but I would expect that the existing sha1 function remains unchanged. How do you keep the compatibility between different programming languages and applications if one use SHA1 and the other uses "hardened SHA-1"?

One alternative is to stop using sha1 :-D

> A large part of the industry has adopted Hardened SHA-1 ...

Do you have examples?
History
Date User Action Args
2018-10-10 21:27:55vstinnersetrecipients: + vstinner, loewis, christian.heimes, antoine.pietri
2018-10-10 21:27:54vstinnersetmessageid: <1539206874.99.0.788709270274.issue34930@psf.upfronthosting.co.za>
2018-10-10 21:27:54vstinnerlinkissue34930 messages
2018-10-10 21:27:54vstinnercreate