#28718: Password reset shouldn't depend on the current password being hashed
with a
supported hasher
------------------------------+--------------------------------------
Reporter: Josh Harwood | Owner: Tim Graham
Type: Bug | Status: assigned
Component: contrib.auth | Version: 1.11
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
------------------------------+--------------------------------------
Changes (by Tim Graham):
* needs_better_patch: 1 => 0
* needs_tests: 1 => 0
Comment:
I think the change to `has_usable_password()` in
703c266682be39f7153498ad0d8031231f12ee79 was unintentional and that adding
a `User.has_disabled_password()` method as originally proposed here will
only add more confusion. I've proposed an
[https://github.com/django/django/pull/9802 alternate PR].
--
Ticket URL: <https://code.djangoproject.com/ticket/28718#comment:8>
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/071.73b2113326b62c71042fc87e76289275%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
