4 ms·
I'm on it right now, would have been done last night but having trouble with rails 3.0 and gem paths. But its not true it wont have any functionality, it does
by KevinMS 16y ago
I'm on it right now, would have been done last night but having trouble with rails 3.0 and gem paths.
But its not true it wont have any functionality, it does what it claims to do, which isn't much, but its something.
Putting
auto_hash :password, :field2, :field3
In a model will automate the process of "cryptofying" (using a fake word to avoid any more terminology disputes)
database fields :password, :field2, :field3 upon save or update
Then it will give you a dynamic accessors like user.password_match?, user.field2_match?
This saves lines of ugly code I don't want to look it, and also frees up the models before_save hook.
Amendment: I think this will make auto_hash the only auth related plugin that defaults to, and only offers, bcrypt
- tptacek 16y agoYeah, bcrypt-ruby already does that, doesn't it?
- KevinMS 16y agoThats up to you to decide, here a comparison: Here is bcrypt-ruby class User < ActiveRecord::Base include BCrypt def password @password ||= Password.new(password_hash) end def password=(new_password) @password = Password.create(new_password) self.password_hash = @password end end Here is auto_hash class User < ActiveRecord::Base auto_hash :password end
- tptacek 16y agoNot sure I'd want to introduce a plugin dep to get rid of 7 lines of code (you don't need the "include"), but, OK.