From c6929bbc9fd8b8f76924cfbdbf4acb333cbeca67 Mon Sep 17 00:00:00 2001 From: Zev Benjamin Date: Thu, 3 Jan 2013 15:43:45 -0500 Subject: [PATCH] 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) --- humbug/settings.py | 1 + 1 file changed, 1 insertion(+) diff --git a/humbug/settings.py b/humbug/settings.py index 3adc2cd5d8..9e3540f4a2 100644 --- a/humbug/settings.py +++ b/humbug/settings.py @@ -280,6 +280,7 @@ if not DEPLOYED: # DEPLOYED PASSWORD_HASHERS = ( 'django.contrib.auth.hashers.SHA1PasswordHasher', + 'django.contrib.auth.hashers.PBKDF2PasswordHasher' ) if DEPLOYED: