phc-discussions - Re: [PHC] Argon2 string encoding and parallelism

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: <5623D88A.6020903@dei.uc.pt>
Date: Sun, 18 Oct 2015 18:36:10 +0100
From: Samuel Neves <sneves@....uc.pt>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Argon2 string encoding and parallelism

On 18-10-2015 18:30, Jean-Philippe Aumasson wrote:
> Just noticed that the string encoding defined by Thomas has a single
> parallelism parameter whereas Argon2 supports distinct number of lanes and
> number of threads, which can't be encoded with a single parameter. I don't
> think that's a problem though, I don't see many reasons why implementations
> wouldnt have #lane=#threads.
>

Number of threads is a runtime parameter that doesn't affect output, so it doesn't really need to be encoded; it's up to
the system configuration/implementation to figure out what the optimal thread count should be. Lanes, on the other hand,
must be there.