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: Fri, 12 Dec 2014 03:30:47 +0000
From: Brandon Enright <>
To: Marsh Ray <>
Cc: "" <>,
Subject: Re: [PHC] How important is salting really?

Hash: SHA1

On Fri, 12 Dec 2014 01:21:32 +0000
Marsh Ray <> wrote:

> C.      Prevents the trivial determination that two accounts chose
> the same password

There are special cases where this point comes into play.  For example,
in the recent Adobe breach an unknown "personalization key" (actually
an encryption key in this case) was used which made cracking
impossible.  But, because of a lack of salting (or in this case CBC +
random IV) it was still possible to determine the password for a large
number of the accounts because the password hints were also leaked.

Salting protects against being able to use information gleaned from
other accounts (like a password hint) from being useful.

I think *everyone* should be using a personalization key with whatever
hashing scheme they pick because without the personalization key a
database leak is nearly harmless.  If the personalization key leaks with
the database then it degrades to as though a key wasn't in use.  That
is, a personalization key is sometimes better, never worse.

But, without password salting a personalization key isn't as effective
due specifically to Marsh's point C.


Version: GnuPG v2


Powered by blists - more mailing lists