phc-discussions - Re: [PHC] Argon2 improvement thread

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: <55B04B4C.50208@dei.uc.pt>
Date: Thu, 23 Jul 2015 03:02:52 +0100
From: Samuel Neves <sneves@....uc.pt>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Argon2 improvement thread

On 23-07-2015 02:43, Solar Designer wrote:
> Do you think we should produce a specification of MAXFORM on its own,
> not merely referring to yescrypt's specification of pwxform with the
> above two parameters fixed at 1, before we decide on accepting it for
> Argon2 tweak?  I'd think the above would be sufficient for the
> decision-making, with the concrete specification of MAXFORM on its own
> only needed as part of a revision of the tweaked Argon2 specification.

The specific parametrization, with reference to pwxform, is good enough for me. I just wanted it to be spelled out. Thanks.