Re:Django-bcrypt
by nicksergeant on Thursday February 03, 2011 @05:28PM
(#2177221)
You sir, are a machine. Steve started working on this 3 feet behind me a little less than 2 hours ago.
It took him two hours to monkey patch a few methods?
Actually the code was already written -- see the bottom of the README.
It took about 30-40 minutes to:
* Add the BCRYPT_ROUNDS setting.
* Remember how to allow for an optional setting (`if foo in settings` and `settings.get(foo, default)` don't work).
* Add the setup.py file.
* Write a README.
* Test with a real Django site to make sure nothing was broken.
* Create and push to repos on BitBucket and GitHub.
> Remember how to allow for an optional setting (`if foo in settings` and `settings.get(foo, default)` don't work).
Instead of:
settings.get(foo, default)
Try: getattr(settings, foo, default)
This looks useful. Thanks.Good idea, pushed!
Re:Django-bcrypt
by nicksergeant on Thursday February 03, 2011 @05:35PM
(#2177251)
I left a few minutes after he started. He very well might've been banging his head against other (client-related) issues within those two hours.
Step 2: Add to INSTALLED_APPS
Step 3: Enjoy more secure password hashing.
...
Step 4: Set BCRYPT_ROUNDS to something higher than 12 when computers get faster.