phc-discussions - Re: [PHC] Proposed timeline changes

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: <CAJm83bBkO8YNA_iBSaEoGV6AJKHHwfwgBKe1L0Bts9cV+duCEQ@mail.gmail.com>
Date: Sun, 5 Jan 2014 12:13:51 -0500
From: Daniel Franke <dfoxfranke@...il.com>
To: Krisztián Pintér <pinterkr@...il.com>
Cc: discussions@...sword-hashing.net
Subject: Re: [PHC] Proposed timeline changes

On 1/5/14, Krisztián Pintér <pinterkr@...il.com> wrote:
>
> Daniel Franke (at Sunday, January 5, 2014, 5:47:36 PM):
>
>> are already finished, and its spec nearly so, but the security and
>> efficiency discussion is not yet written.
>
> however, those are not requirements.

The call for submissions says otherwise:

Submission Requirements
--------------------------------------

[...]

Initial security analysis

* Discussion of the security claims and usage constraints of the
proposed algorithm: For which usage scenarios do the designers claim
their algorithm secure, and when should it not be used?
* Discussion of the security of the algorithm, and its dependence on
the security of cryptographic primitives used by the algorithm.

Efficiency analysis

* Discussion of the performance of the scheme on the target platforms
(that is, mainstream software): expected speed of an optimized
implementation, ability to exploit modern CPUs features (SIMD or
multicore), etc.
* Discussion of the performance of the algorithm on platforms that may
be used for high-speed password cracking (ASIC, FPGAs, GPUs); if
possible, an argument why password-cracking on those platforms is not
quite cost-effective.