[issue5212] Incorrect note about md5 in hmac module documentation

Georg Brandl added the comment: Removed note in r85617. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Pyt

[issue5212] Incorrect note about md5 in hmac module documentation

Terry J. Reedy added the comment: The supposed 'known weaknesses'. I have no particular opinion. Anyway, we have your recommendation: remove the note. I will let others defend it. -- ___ Python tracker

[issue5212] Incorrect note about md5 in hmac module documentation

.:. brainsik added the comment: Since the note is incorrect, it seems like it should be removed. What "results it is based on" are you referring to and what complaints are you concerned about? -- ___ Python tracker

[issue5212] Incorrect note about md5 in hmac module documentation

Terry J. Reedy added the comment: Are you proposing that the note be removed entirely (and ignore the results it is based on) or just reworded? If it were removed, I could imagine complaints. If reword, specifically how? -- assignee: georg.brandl -> d...@python nosy: +d...@python, tjr

[issue5212] Incorrect note about md5 in hmac module documentation

Changes by Terry J. Reedy : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5, Python 3.0 ___ Python tracker ___ ___ Python-

[issue5212] Incorrect note about md5 in hmac module documentation

.:. brainsik added the comment: Bruce Schneier also says (regarding the SHA-1 collision attacks), "it doesn't affect applications such as HMAC where collisions aren't important": http://www.schneier.com/blog/archives/2005/02/sha1_broken.html ___ Python track

[issue5212] Incorrect note about md5 in hmac module documentation

New submission from .:. brainsik : The HMAC module page [1] says: Note: The md5 hash has known weaknesses but remains the default for backwards compatibility. Choose a better one for your application. However, according to the "Hash Collision Q&A" [2] linked to from the hashlib module [3], md5