Reinier Balt wrote: > One problem I see is when people want to downgrade. You chop the > password field back to 40 chars, but it will cause all users incapable > of logging in. Perhaps we can put a default password in the password on > migration.down? like sha1('secret123') so we leave Tracks operable on > downgrade? #26 (comment)
This commit catches Factory::DuplicateDefinitionErrors raised by factory_girl 2.1.0. See the following thread for some background. http://groups.google.com/group/factory_girl/browse_thread/thread/4df21d9240c20198
Expressions '...should == @user' caused specs to fail because of ArgumentError in 'User authentication resets password' wrong number of arguments (0 for 1) Replacing expectations declared for User objects with expectations declared for their id fields solves the problem and doesn't change specs' logic.
BCrypt is regarded as a more secure alternative to hashing using message digest algorithms, such as MD5 and SHA families [0, 1, 2]. Apart from built-in salting it is adaptable to the increasing power of modern processing units, which makes it more secure against brute-force cracking. This commit makes all passwords hashed using BCrypt. The session tokens remain generated using SHA1. Tests were updated, `rake test:units` and `rake test:functionals` didn't report any regressions.  http://bcrypt.sourceforge.net/  http://en.wikipedia.org/w/index.php?title=Bcrypt&oldid=439692871  https://github.com/codahale/bcrypt-ruby/blob/eab1c72/README.md
…e the action you want to take on a todo, including deferring
…jects work in the new done views
need to figure out how to restore this...