Zev Benjamin c6929bbc9f Allow PBKDF2 password hashes in dev mode ... This fixes a problem where if you were 1) running in development mode, 2) had populated the database from production data, and 3) tried to log in with an account that had changed its password, you wouldn't be able to. The problem was that the password change created a password change record with a PBKDF2 hash, not a SHA1 hash. This change lets the dev server accept PBKDF2 hashed passwords, but still use SHA1 password hashes for creating test users for speed. (imported from commit 2840d266f93add1edbba7f93a7f1491372fc8cf1)		2013-01-03 16:03:55 -05:00
..
__init__.py	Initial Django commit: basic account, zephyr stream, narrowing, etc.	2012-08-28 12:44:51 -04:00
backends.py	Allow case-insensitive email addresses when doing authentication	2012-12-04 16:37:55 -05:00
ratelimit.py	Use datetime.min for initial last_error rather than int 0.	2012-12-11 15:59:08 -05:00
settings.py	Allow PBKDF2 password hashes in dev mode	2013-01-03 16:03:55 -05:00
test_settings.py	Decrease get_updates timeout for client test suite	2012-12-14 16:22:42 -05:00
urls.py	Log password change events via the password reset feature.	2012-12-13 15:22:35 -05:00
wsgi.py	Remove more commented out example code	2012-10-29 23:21:00 -04:00