Hi, On Thursday, February 4, 2016 at 6:22:09 PM UTC+1, Raphaël Barrois wrote: > > Just as djangoproject.com might need to keep those old hashers around, > many projects will need it as well. > As such, providing the hashers in a dedicated "legacy" package might be > the solution for most projects. >
I'd be surprised if we still have unsalted hashes, that said, there is no reason to keep the old hashers around, you can easily upgrade them to pbkdf2 without requiring the user to log in (we actually did the same for salted sha when we upgraded $site). Cheers, Florian -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3e404d64-8d06-453e-811c-6575747685e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
