phc-discussions - Re: [PHC] Why protect against side channel attacks

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-u5d5MR5emE9mVzDwbKQO0=fB-hm1Ru0e2rqCfOtTaV5bQ@mail.gmail.com>
Date: Thu, 25 Jun 2015 03:20:46 +0100
From: Peter Maxwell <peter@...icient.co.uk>
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Re: [PHC] Why protect against side channel attacks

On 25 June 2015 at 02:18, Bill Cox <waywardgeek@...il.com> wrote:

> On Wed, Jun 24, 2015 at 5:55 PM, Marsh Ray <maray@...rosoft.com> wrote:
>
>>  Again, these cache timing side channels tend to leak the salts too.
>>
>
> How?  In most cases, salt never leaves the authentication servers and
> associated storage.  The salt is hashed/shredded before unpredictable
> addressing begins.
>

So the timing-attack recovers the hash of the salt just before the
data-dependent path.  That's, theoretically, reduced the difficulty of the
problem back to the constant-time portion of the PDF.  (it's not
particularly practicable and quite a remote possibility but many of the
topics discussed on this list have been of a similar nature)

Content of type "text/html" skipped