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: <2772.1389256500@critter.freebsd.dk>
Date: Thu, 09 Jan 2014 08:35:00 +0000
From: "Poul-Henning Kamp" <phk@....freebsd.dk>
To: discussions@...sword-hashing.net, Bill Cox <waywardgeek@...il.com>
Subject: Re: [PHC] A final cheat killer pass with smoke

In message <CAOLP8p5QPOhQGQcBqPAMMYLHWK+cv4xZ9wsZ=f59WfPiehfimA@...l.gmail.com>
, Bill Cox writes:

>I am assuming the attacker cannot determine the addresses accessed, but
>only that a cache miss occured.  I'm pretty new to this stuff.  Is there a
>cache timing attack that reveals the actual addresses?

To varying degrees.  You should at least assume that the address can be
exposed to a VM page size granularity, and for safety I would assume
cache-line granularity also.

Colin Perceivals paper on cache-misses on Intels HTT would be a good
introduction.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@...eBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.