Re:Coding Horror: You're Probably Storing Passwords Incorrectly
by bct on Monday September 17, 2007 @05:56PM
(#55917)
Better yet, use OpenID and let somebody else worry about passwords.
(ok, this isn't an option for everybody yet)
Re:Coding Horror: You're Probably Storing Passwords Incorrectly
by gwenhwyfaer on Monday September 17, 2007 @02:17PM
(#55819)
Is there a list of these somewhere? Which ones would you recommend?
Re:Coding Horror: You're Probably Storing Passwords Incorrectly
by thomasptacek on Monday September 17, 2007 @02:44PM
(#55834)
If you ship on Unix, use what your operating system ships with. Failing that, use bcrypt, or PHK's MD5 scheme. If you must DIY, iterate the hash function several thousand times.
Re:Coding Horror: You're Probably Storing Passwords Incorrectly
by davidw on Monday September 17, 2007 @12:13PM
(#55742)
> Lesson: use someone else's (good) password system.
Ok, what? I use Ruby on Rails, and I want something open source. What do you recommend?
Re:Coding Horror: You're Probably Storing Passwords Incorrectly
by thomasptacek on Monday September 17, 2007 @12:26PM
(#55748)
Acts_as_authentable uses bcrypt.
Re:Coding Horror: You're Probably Storing Passwords Incorrectly
by aston on Monday September 17, 2007 @11:25AM
(#55712)
If your bank only uses a username/password combo to confirm your identity online, you need a new bank.
Re:Coding Horror: You're Probably Storing Passwords Incorrectly
by thomasptacek on Monday September 17, 2007 @11:29AM
(#55716)
If you use the same password for your web 2.0 recipe account as your bank, etc, etc, etc. We shouldn't rationalize this stuff. All I'm saying is, don't make mistakes with your password system; use someone else's (good) password scheme.
Lesson: use someone else's (good) password system.