You're referring to a "pepper" - a site wide secret that's supposed to be used, in some way, to further encrypt passwords. As far as I'm aware there are no algorithms available that take a pepper into consideration. Further, I don't see the need for the inclusion of a pepper if the password encrypting function is solid. If we've selected the right algorithm and the right complexity (time and memory) then the time to brute force a single password is still going to be orders of magnitude out of reach.
http://blog.ircmaxell.com/2012/04/properly-salting-passwords-case-against.html http://security.stackexchange.com/questions/41754/what-is-the-purpose-of-a-pepper http://security.stackexchange.com/questions/3272/password-hashing-add-salt-pepper-or-is-salt-enough On Tuesday, 9 June 2015 15:16:02 UTC+10, Ram Rachum wrote: > > Hi, > > What do you think about using the project's `SECRET_KEY` as an additional > salt in Django's password hashers? The advantage would be that they'll be > harder to crack, as an attacker would need access both to the database > table and the code for the secret key. The disadvantage I can think of is > that you couldn't change your `SECRET_KEY` without breaking old passwords > (so maybe we need a separate secret in the settings.) > > What do you think? > > > Thanks, > Ram. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c1ec72af-6840-41d6-9c7b-9632baaa5aa0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
