On 15 juin 2013, at 15:17, Jon Dufresne <[email protected]> wrote:
> I guess I need to decide which way to go. Either a custom password hasher > that uses a static salt, or use Django's existing password hasher and not > think about it. The first option is a very thin addition on top of Django's authentication framework. Many parts of Django are pluggable precisely to allow such customizations. I view it as standing on the shoulders of giants rather than NIH. To make the migration easier, you'll probably put your current salt value in a setting distinct from SECRET_KEY. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" 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. For more options, visit https://groups.google.com/groups/opt_out.
