phc-discussions - Re: [PHC] Specification of a modular crypt format

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: <CALW8-7+hz-58YdAEoRZ=ArM9JYL2UBfkrTEGf1tZy9-_-3FzJw@mail.gmail.com>
Date: Mon, 28 Sep 2015 13:50:25 +0200
From: Dmitry Khovratovich <khovratovich@...il.com>
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Re: [PHC] Specification of a modular crypt format

On Sun, Sep 27, 2015 at 11:20 PM, Alexander Cherepanov <ch3root@...nwall.com
> wrote:

>
>>
> Hm, there seems to be some indeterminism in Argon2 itself here? According
> to spec: "The actual number of blocks is $m'$, which is $m$ rounded down to
> the nearest multiple of $4p$."


 To ease the hashing process, Argon2 allocates the same amount of memory
for each thread. Therefore, when you request 9 or 10 KB of memory and 2
threads, 8 KBytes will be used in fact. The output values will be
different, of course, as the requested 'm' is hashed as well.


-- 
Best regards,
Dmitry Khovratovich

Content of type "text/html" skipped