#20917: Change the password hashers when testing
-------------------------------------+-------------------------------------
Reporter: mjtamlyn | Owner:
Type: New feature | ashchristopher
Component: Testing framework | Status: assigned
Severity: Normal | Version: master
Keywords: | Resolution:
Has patch: 0 | Triage Stage: Accepted
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by anonymous):
I'm not sure "backwards compatibility" needs to be kept in this instance.
Nothing is really broken by the change, unless somebody is manually
inspecting the hash. In this case, fast by default may be the best
solution. (But maybe keep the MD5 hasher instead of a no-op hasher, just
in case somebody is doing something incredibly stupid.)
--
Ticket URL: <https://code.djangoproject.com/ticket/20917#comment:5>
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/066.5e10ad323a14c4c8c6e5c134c61327ba%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.