Re:How To Safely Store A Password
by aidenn0 on Tuesday December 14, 2010 @01:07PM
(#2005052)
That article actually states that salting is a real security practice, is a necessity, and that it's been in UNIX since 1976,
[ Parent
| on HN ]
He may be saying that because I've been making fun of people who use the word "salt" (in most other situations, crypto people would call that a "nonce"); I have in the past made the point that real crypto people never say "salt".
But then Eli Biham used the term extensively in his HAIFA framework and I lost the argument. I'll still make fun of the word (salt! smoked salt! peanut salt! hah!), but I can't say no crypto people use it. I wish they wouldn't, though.
That argument sounds like the German balloon fliers, who insist that they "fahren" (drive) the balloon and don't "fliegen" (fly) it.
I was more talking about bcrypt being consensus with that post. Salting slows down cracking attempts by a factor of N where N is the length of the hash; md5 and sha1 are so fast that you shouldn't be banking on salting to protect you in 2010. Also, you should assume that if an attacker has your database (with salts), they also have your code, which tells them exactly how the salt was applied. In that case, salting doesn't slow you down at all.
But you're talking about defending against brute force attacks? Salting's strength is in defending against rainbow tables. It seems the best policy at this point is to use both as they defend against different things and are not mutually exclusive.
Re:How To Safely Store A Password
by bostonvaulter2 on Tuesday December 14, 2010 @01:47PM
(#2005225)
I think the point is that you should use bcrypt and salt at the same time.
You don't need to do anything like that; bcrypt does all this stuff for you. Don't salt bcrypt.