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  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: Thu, 28 Aug 2014 17:21:20 +0200
From: Krisztián Pintér <>
To: "" <>
Subject: Re: [PHC] What Microsoft Would like from the PHC - Passwords14 presentation

On Thu, Aug 28, 2014 at 5:59 AM, Rade Vuckovac <> wrote:

> 1st it is relatively easy to allocate non-cacheable memory (comparing to
> keeping everything in cache). It is not portable but it seems that every
> major OS supports that option.

1. imagine the documentation saying "and you need to allocate
non-cached memory from the OS". most of the time we don't even
allocate memory, we let the runtime environment do it.

2. testing is a bit problematic. how do you test if it is cached? you
attempt timings?

3. what about virtual OSs? i don't think the host OS respects such requests.

Powered by blists - more mailing lists