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.

classification
Title: The external link to a "Hash Collision FAQ" points to some company's homepage
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, georg.brandl, stutzbach
Priority: normal Keywords:

Created on 2010-05-21 20:09 by stutzbach, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg106259 - (view) Author: Daniel Stutzbach (stutzbach) (Python committer) Date: 2010-05-21 20:09
At the bottom of the documentation for hashlib, there's a link to
http://www.cryptography.com/cnews/hash.html

which the hashlib documentation describes as "Hash Collision FAQ with information on which algorithms have known issues and what that means regarding their use."

However, the page at that link is identical to http://www.cryptography.com/

which is just the homepage of some company that happens to deal with cryptography.  If they do in fact host a Hash Collision FAQ, I couldn't find it. :-(

Googling for "Hash Collision FAQ" (with quotes) mostly turns up references to the Python documentation, so I'm guessing the intended document no longer exists.

The following wikipedia link might be an OK substitute, although it makes for pretty dense reading.
http://en.wikipedia.org/wiki/Cryptographic_hash_function#Cryptographic_hash_algorithms
msg106260 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2010-05-21 20:25
The FAQ can still be found in the internet archive, http://web.archive.org/web/20070928160638/http://www.cryptography.com/cnews/hash.html

but of course this is not a good link, especially because it's not updated.  I've added the link to the wikipedia article, as you suggested, in r81404.  It should be a good starting point for further research.
History
Date User Action Args
2022-04-11 14:57:01adminsetgithub: 53029
2010-05-21 20:25:49georg.brandlsetstatus: open -> closed

nosy: + georg.brandl
messages: + msg106260

resolution: fixed
2010-05-21 20:09:37stutzbachcreate