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]
Date: Fri, 19 Sep 2014 16:08:05 +0200
From: Krisztián Pintér <>
To: "" <>
Subject: Re: [PHC] Missed opportunity re: unpredictable addressing?

On Fri, Sep 19, 2014 at 5:59 AM, Alex Elsayed <> wrote:
> In particular, a salt is defined as 1.) public and 2.) random. I suspect
> that salt-dependent, password-independent addressing might well prove a
> useful trick.

the problem is exactly that salt should be treated as public. this
concept would be fine for secret salts, which is an option, but
unusual. for public salts, it does not help, but hinder. why it does
not help, was explained by Dmitry. let me explain why it hurts.

predictable but wildly irregular pattern is harder to optimize, but
can be optimized. it is typically a situation which urges the good
guys to omit optimization (to avoid complexity), but urges attackers
to do the optimization, and thus gain advantage. we want optimization
options to either be not there, or so easy that everybody will
implement them. difficult optimizations mean advantage to attackers,
and disadvantage to defenders.

Powered by blists - more mailing lists