phc-discussions - Re: [PHC] Analysis of Argon2i

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] [day] [month] [year] [list]

Date: Wed, 13 Jan 2016 22:48:11 +0100
From: Krisztián Pintér <pinterkr@...il.com>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] Analysis of Argon2i

Bill Cox (at Wednesday, January 13, 2016, 10:34:34 PM):
> I like the idea of XORing over memory for Argon2i.  Both Lyra2 and Gambit did this.

and for a reason!

in http://article.gmane.org/gmane.comp.security.phc/1386 i wrote:

"if you overwrite, the slot becomes unused for a while. i mean, once
it has been read, and until it gets a new value, it just sits there
unused. at any point in time, a certain fraction of the memory (and a
quite huge fraction) is in this idle state. if you cleverly reuse
memory slots, you can run the algorithm with smaller memory footprint.
i prevent this by never discarding any value."