phc-discussions - Re: [PHC] Argon2

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: Tue, 05 May 2015 16:29:25 +0000
From: Jean-Philippe Aumasson <jeanphilippe.aumasson@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Argon2

Padding was changed too iirc
On Tue 5 May 2015 at 18:26 Krisztián Pintér <pinterkr@...il.com> wrote:

>
>
>
> Jean-Philippe Aumasson (at Tuesday, May 5, 2015, 4:59:35 PM):
> > To clarify: I'd talk of optimizations rather than tweaks, after
> > we've selected the winner. I'm not planning another round of tweaks
> > and evaluations that would delay the process. If the panel selects
> > some Argon2 variant as a winner, the final version may be optimized
> > jointly with the authors. A bit like Keccak/SHA3 was optimized after
> being selected by NIST.
>
> just ftr sha3 was not optimized after selection. the original nist
> draft chose a different parametrization of keccak. but it was a
> totally legit keccak instance. and the reason was that their
> requirements wasn't carefully stated, so they fixed that, and
> reparametrized keccak accordingly.
>
>

Content of type "text/html" skipped