phc-discussions - 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-next>] [day] [month] [year] [list]

Message-ID: <CAGiyFdcroE23kZX=OhjEmzGhTLan+xdj_xqhv1ccz71=uY=nZw@mail.gmail.com>
Date: Sun, 18 Oct 2015 17:30:13 +0000
From: Jean-Philippe Aumasson <jeanphilippe.aumasson@...il.com>
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Argon2 string encoding and parallelism

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.

Content of type "text/html" skipped