phc-discussions - Re: [PHC] Do we need a common password hashing API?

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]

Date: Sun, 13 Apr 2014 08:42:27 -0400
From: Bill Cox <waywardgeek@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Do we need a common password hashing API?

On Sun, Apr 13, 2014 at 1:32 AM, Justin Cappos <jcappos@....edu> wrote:

> Some of the arguments of PolyPassHash are not overly sensible outside the
> context of this algorithm.   For example, the number of shares, whether an
> account is thresholdless or a threshold account, etc.
>
> I think for many of the other algorithms what you say makes sense though.
>
> Justin
>

There are a few entries that are difficult to fit into the PHS interface.
 For example, Parallela has two time parameters that are bitwise OR-ed to
form t_cost, though I would have prefered that he just use m_cost (an
unused parameter) as the second time cost.  Several others have multiple
hard-coded constants to set various features to default values.  Maybe a
generic dictionary (attribute list) should be part of the interface to set
those parameters.  I'm not sure.

Bill

Content of type "text/html" skipped