Re:Exploring Rails 3.1 - ActiveModel::SecurePassword
by there on Saturday April 16, 2011 @09:04PM
(#2455307)
This move also signals to the community that bcrypt is considered a best practice, important enough that it's included by default.
bcrypt has been considered a best practice for quite a while. it's been openbsd's default password hashing scheme since 1997, and used in a number of php projects like drupal, phpbb, and wordpress for many years.
Re:Exploring Rails 3.1 - ActiveModel::SecurePassword
by swaits on Saturday April 16, 2011 @10:40PM
(#2455436)
Yup. That hasn't stopped hordes of devs from doing stupid things with passwords. My point is that now, at least for Rails, bcrypt is harder to ignore. And that's a good thing.
bcrypt has been considered a best practice for quite a while. it's been openbsd's default password hashing scheme since 1997, and used in a number of php projects like drupal, phpbb, and wordpress for many years.