News for hackers. Stuff that matters.
Re:How To Safely Store A Password by barefoot on Friday July 01, 2011 @09:27AM (#2718210)
Hashing passwords on the client indicates that the salt is available to the client. In the event of a database compromise it's guaranteed then that the attacker will have the salt and be able to crack your passwords.

If the salt is stored on the server, in a login.php script for example, and there is (just) a database compromise then an attacker will be at a disadvantage because they will need to figure out the salt first before cracking any of the passwords.

In fact, this is something being ignored here quite a bit. A number of potential attacks only lead to the database - or part of it - being exposed. If you have a large enough salt stored in your unaffected code base then an attacker is going to have a hard time.

Re:How To Safely Store A Password by nlco on Friday July 01, 2011 @10:34AM (#2718471)
Salts are suppose to be considered public. For the most part, they are defenses against rainbow tables and to make an attacker have crack each password individually.
Re:How To Safely Store A Password by zagaberoo on Friday July 01, 2011 @12:09PM (#2718881)
Exactly; Having a secret hash is just another example of futile security through obscurity. You want an attacker to be able to know as many parts of the puzzle as possible and still be thwarted.
Re:How To Safely Store A Password by barefoot on Friday July 01, 2011 @09:08PM (#2720750)
Agreed, but an important part of the article was that even public salted md5 passwords are ineffective.