#26187: Remove weak password hashers from the default PASSWORD_HASHERS setting
-------------------------------------+-------------------------------------
Reporter: timgraham | Owner: timgraham
Type: | Status: assigned
Cleanup/optimization |
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by claudep):
Looking at a rather old app of mine with many users, I see that the only
weak hasher still used is salted SHA1. Just wondering if this is simply an
isolated example or if this matches the experience of many other projects.
In the latter case, we might consider letting this hasher for the next one
or two versions. Apart from that question, the patch looks good.
--
Ticket URL: <https://code.djangoproject.com/ticket/26187#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.5ffa3b19b30c47617ff185718fa388b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
