News for hackers. Stuff that matters.
Re:How To Safely Store A Password by ax0n on Tuesday December 14, 2010 @12:53PM (#2004994)
In a case like the Gawker incident, it isn't safe. If the source code to the password hashing algo is compromised (it was) then the salt becomes useless. In short, just use bcrypt.
Re:How To Safely Store A Password by Xk on Tuesday December 14, 2010 @12:55PM (#2005007)
No. No no no.

The source code to the hashing algorithm means nothing. It is already open source!

The reason that the salt is there is to prevent against rainbow tables.

The salting did NOT become useless. If they had not salted passwords, then many many more passwords would have been broken because instead of having to brute force each and every one, you'd just look it up in a massively large hash table.

Re:How To Safely Store A Password by jrockway on Tuesday December 14, 2010 @05:48PM (#2006073)
No, he thinks the salt is stored secretly in the source code. Of course, it's not; you store it right next to the hash so that you don't have to use the same salt for every password.
Re:How To Safely Store A Password by aidenn0 on Tuesday December 14, 2010 @01:02PM (#2005036)
Salting and choice of hashing algorithm are orthogonal. If it takes X amount of time to brute force a password of strength Y and you do salt, then an attacker can crack N passwords of strength Y in time NX. If you don't salt, then an attacker can crack all* passwords of strength Y in time N, which is a huge difference.
Re:How To Safely Store A Password by ax0n on Tuesday December 14, 2010 @01:07PM (#2005053)
Alas, I stand corrected. Thanks. At the same time, the author does have a good point that very slow algorithms are fundamentally better for security, but I'm glad you pointed this difference out. Classic case of me not thinking things all the way through.