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: Mon, 10 Nov 2014 16:13:18 +0100
From: Sascha Schmidt <sascha.schmidt@...-weimar.de>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Another PHC candidates "mechanical" tests

Hi.

>- I tried to visualize real used memory (measured by rusage()) and
>run time with variable mcost/tcost (and generate some fancy graphs:-)

Judging from our graphs you might have confused the instances of
Catena. Catena-DBG should require about 1.5 times the size of
Catena-BRG and it does so in our tests. Also Catena and Catena-BRG
should be absolutely equal in all categories.


>>  - Catena/Catena2 implementations allows to produce hash of length >256 bytes, which is apparently wrong
>
>
> The output length of Catena is limited to the output length of
> underlying hash function. Hence, for Blake2b and SHA512 the max output
> length is 64-byte.
We actually made a small mistake there. The fix is already on my
github repository and should be merged into the main one soon.


Sincerely
Sascha Schmidt
Catena Code Monkey