phc-discussions - Re: [PHC] Another PHC candidates "mechanical" tests

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: Wed, 25 Mar 2015 07:53:49 +0300
From: Solar Designer <solar@...nwall.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Another PHC candidates "mechanical" tests

On Tue, Mar 24, 2015 at 11:09:39PM +0100, Milan Broz wrote:
> On 03/24/2015 04:45 AM, Solar Designer wrote:
> > 
> > Thus, yescrypt v1's output for a shorter length is always a prefix of
> > its output for a longer length.  I'd appreciate you re-testing yescrypt
> > for this property.
> 
> This test is output from original submission (with special case):
> https://github.com/mbroz/PHCtest/blob/master/output/Lenovo_X230_i5_4G/o_len/yescrypt.dat
> 
> And now the version 1:
> https://github.com/mbroz/PHCtest/blob/master/output/round2_Lenovo_X230_i5_16G/o_len/yescrypt.dat
> https://github.com/mbroz/PHCtest/blob/master/output/round2_Lenovo_X230_i5_16G/o_len/yescrypt-sse.dat
> 
> So it works as expected.

Thanks!  It would also be helpful if you test the same for g > 0, which
exposes additional relevant code paths that are not available via PHS().

Alexander