| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20150405214133.GA10559@openwall.com> Date: Mon, 6 Apr 2015 00:41:33 +0300 From: Solar Designer <solar@...nwall.com> To: discussions@...sword-hashing.net Subject: wiki Hi, I've recently updated the wiki page on yescrypt for v1, and I've just added some pseudocode illustrating a typical yescrypt invocation - that way, it actually looks quite simple: https://password-hashing.net/wiki/doku.php/yescrypt I tried to keep the pseudocode notation similar to what's already used on the wiki for other candidates. While at it, I noticed that these wiki pages have broken download links (not updated to current versions, so giving 404): https://password-hashing.net/wiki/doku.php/argon https://password-hashing.net/wiki/doku.php/catena https://password-hashing.net/wiki/doku.php/lyra2 https://password-hashing.net/wiki/doku.php/parallel https://password-hashing.net/wiki/doku.php/pomelo https://password-hashing.net/wiki/doku.php/pufferfish These are missing pseudocode: https://password-hashing.net/wiki/doku.php/parallel https://password-hashing.net/wiki/doku.php/pomelo https://password-hashing.net/wiki/doku.php/pufferfish The pseudocode for Parallel should be particularly easy to add. Steve? That's for finalists only. Perhaps there are similar issues with many non-finalist wiki pages as well. Alexander
Powered by blists - more mailing lists