FWIW the idea is relatively old and I think mozilla has a 3rd party app which just adds that functionality to the hashers. As far as I remember it even allows having multiple secrets and as such migrate to a new key.
On Tuesday, June 9, 2015 at 7:16:02 AM UTC+2, 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/1fb3fcb0-861f-40d9-a111-d974f612ab3e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
