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] [day] [month] [year] [list]
Date: Sun, 18 Oct 2015 17:39:26 +0000
From: Jean-Philippe Aumasson <>
Subject: Re: [PHC] Argon2 string encoding and parallelism

So we'll accept a same encoding for instances whose implementations has a
different structure. Unlikely to be an issue I guess.

On Sun, Oct 18, 2015 at 7:37 PM Samuel Neves <> wrote:

> 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.

Content of type "text/html" skipped

Powered by blists - more mailing lists