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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 2 Apr 2015 22:56:37 +0200 (CEST)
To: "" <>
Subject: Re: [PHC] Panel: Please require the finalists to help with

On Thu, 2 Apr 2015, Dmitry Khovratovich wrote:

> Thus I would insist on hardcoding the number of rounds, hash function 
> type, flags, etc. into the PHS() call. The designers should make a 
> choice.

I kind of agree, there can be too much choice. On the other hand, no 
designer is able to guess how much memory the user (or, more likely, the 
sysadmin) is willing to donate for password hashing, and how much time the 
user (or the sysadmin) is willing to spend for password hashing ... and 
even when the time is fixed, some tool is needed to conveniently fix the 
time parameter. This is what Catena-Axungia is for

... and yes, this is for Catena, but of course, something similar could 
(or, as I would claim, should!) be build for the other candidates as well.

So long


------  I  love  the  taste  of  Cryptanalysis  in  the morning!  ------
--Stefan.Lucks (at), Bauhaus-Universit├Ąt Weimar, Germany--

Powered by blists - more mailing lists