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  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: Wed, 22 Jul 2015 15:33:59 -0700
From: Bill Cox <>
To: "" <>
Subject: Re: [PHC] Argon2 improvement thread

On Wed, Jul 22, 2015 at 2:12 PM, Jean-Philippe Aumasson <> wrote:

> There's been some additions to the document, mainly by Bill (thanks!)
> There's 3 main tweaks proposed to the algorithm:
> 1. blamka
> 2. maxform
> 3. non-linear indexing
> Point 3. looks like a no-brainer to me; any objection?

No objection here.  I would be surprised to hear any.

> @Bill, Solar (and others): blamka and maxform, respectively in Argon2i and
> 2d, is that what you have in mind, of maxform in both?

I think I would prefer maxform in both, with the regular reduced-blake2 in
both, although using blamka in both would also be OK.  I'm a big fan of
maxform with or without blamka, and also I would prefer to keep Argon2i
similar to Argon2d, preferably merging the algorithms into 1.  Even though
the addressing in Argon2i is predictable, I do not see any easy way to use
in a GPU against maxform, though I'm no GPU expert.


Content of type "text/html" skipped

Powered by blists - more mailing lists