| This is thetalk page for discussing improvements to theCryptography hash template. |
|
Seems like notable SHA-3 candidates should be on a separate line from non-SHA-3 hashes. They're notable for different reasons from the old hash functions, and they're currently new and unanalyzed.
For what it's worth.(Unsigned by IP 75.24.109.96 on 2 December 2008)
Where wouldSipHash fit in this table? I would say under MAC functions, but I am not an expert on the subject. --Yxejamir (talk)13:58, 19 January 2017 (UTC)[reply]
For a while now,BLAKE2 has been listed as a “common” hash function. Do we have areliable source which supports the assertion that Blake2 is, indeed, a commonly used hash?
The sense I get is that the most commonly used hash these days is SHA256 (SHA-2-256, if you will), since SHA-1 and MD5 (the previously two commonly used hashes) were broken.Samboy (talk)10:24, 1 October 2018 (UTC)[reply]
If we’re going to haveNMAC on this list, I would like to see a Wikipedia article about NMAC (or even just a section inHMAC describing what an NMAC is) written first.Samboy (talk)15:21, 6 October 2018 (UTC)[reply]
This section only talks about password KDFs and password hashing functions (bcrypt andcrypt). These should all be moved to a new section called "Key stretching functions" andHKDF should be added to "Key derivation functions".Catena,Makwa, andyescrypt are just redirects toPassword Hashing Competition and should be removed from the template.Lyra2 is a low quality page and should probably be removed from the template.NotSc00bz (talk)23:52, 2 January 2020 (UTC)[reply]
The KDF section should be named:
"Password hashing/
key stretching functions", moveLM hash into it, and remove key stretching from utilization section since it has its own section now. Then add a new KDF section with justHKDF. I'll make this changes in a week if no one disagrees. We should still think about removingCatena,Makwa,yescrypt, andLyra2 for being just redirects toPassword Hashing Competition or having a low quality page.NotSc00bz (talk)04:19, 4 January 2020 (UTC)[reply]