phc-discussions - Re: [PHC] A final cheat killer pass with smoke

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: <CA+aY-u4qJ8Zh66wR0u0y=XeYHPdT=zVQzbBT1596TNoJQ5DwZA@mail.gmail.com>
Date: Thu, 9 Jan 2014 00:56:00 +0000
From: Peter Maxwell <peter@...icient.co.uk>
To: discussions@...sword-hashing.net
Subject: Re: [PHC] A final cheat killer pass with smoke

On 8 January 2014 14:56, Bill Cox <waywardgeek@...il.com> wrote:

>
>
> So, after my threads finish filling memory with their hashed data, I could
> run a "cheat killer" pass that randomly accesses all of the hash data in a
> pattern that depends on the password, making it impossible to pre-compute.
>

So... this memory access pattern that depends on the password ;-)   If you
access pattern is dependent on the password, does that not put you back to
square one with side-channel attacks, so to speak?

Content of type "text/html" skipped