phc-discussions - Re: [PHC] Panel: Please require the finalists to help with benchmarks

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.11.1504022242530.327@debian>
Date: Thu, 2 Apr 2015 22:56:37 +0200 (CEST)
From: Stefan.Lucks@...-weimar.de
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Re: [PHC] Panel: Please require the finalists to help with
 benchmarks

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

   https://github.com/medsec/catena-axungia

... 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

Stefan

------  I  love  the  taste  of  Cryptanalysis  in  the morning!  ------
uni-weimar.de/de/medien/professuren/mediensicherheit/people/stefan-lucks
--Stefan.Lucks (at) uni-weimar.de, Bauhaus-Universität Weimar, Germany--