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: <E1YTN3j-0000lZ-Bc@login01.fos.auckland.ac.nz> Date: Thu, 05 Mar 2015 17:06:51 +1300 From: Peter Gutmann <pgut001@...auckland.ac.nz> To: discussions@...sword-hashing.net Subject: Re: [PHC] PHC output specifics Marsh Ray <maray@...rosoft.com> writes: >I posted this to the panel list, but we’d like to move the discussion here. My response in the panel list was "+". >At the same time I’d like to clarify: Where I listed three specific knobs, I >was not so much trying to specify the behavior of the function and just give >examples. Having had to implement, test, and maintain a new gratuitously incompatible password PRF for every single security protocol I've implemented that uses them (PGP, SMIME, SSH, SSL, and CMP) I'd really like the number of knobs kept to a minimum, perhaps one for CPU use and one for memory use and that's all. The less bells and whistles, the better. Peter.
Powered by blists - more mailing lists