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] [thread-next>] [day] [month] [year] [list]
Date: Thu, 27 Feb 2014 20:37:42 +0000
From: Samuel Neves <>
Subject: Re: [PHC] "Predictable" vs "pseudorandom" KDFs

On 27-02-2014 20:11, Solar Designer wrote:
> How about "cache timing safe" and "cache timing unsafe"?

That is probably the clearest and least ambiguous option. I don't like
"predictable" and "pseudorandom", those terms don't need more overloads.
For the sake of bike-shedding, I propose "silent" and "noisy".

Powered by blists - more mailing lists