phc-discussions - Re: [PHC] An additional PHS API to include a string?

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: <CAGiyFddVVye=dWJtEAfEi8d4Th4Ycy-5eXOWHLGvc6xgprB8WA@mail.gmail.com>
Date: Sun, 31 Aug 2014 16:48:26 +0200
From: Jean-Philippe Aumasson <jeanphilippe.aumasson@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] An additional PHS API to include a string?

>
> Ideally, PHC should concentrate on the cryptographic qualities of the
> candidates, using code made for research, not for production.
> Production-ready implementations will come later on, for the winner(s),
> and these will include a simplified string-based API. Developers at
> large will cautiously wait for these implementations to emerge, and use
> them.
>

FTR, I share that point of view: PHC is mainly a competition for an
algorithm, not for a production-ready piece of software. The
possibility of user-friendly interfaces will be taken in consideration
when selecting the winner(s). Regarding string-based APIs, we expect
string formatting/encoding/packing components to be largely agnostic
of the underlying hash algorithm.