#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
------------------------------+--------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"43348e4aa16834d0456e7c9f593e6c5e5447bcd3" 43348e4a]:
{{{
#!CommitTicketReference repository=""
revision="43348e4aa16834d0456e7c9f593e6c5e5447bcd3"
Reverted "[2.0.x] Expanded docs for
AbstractBaseUser.has_usable_password()."
This reverts commit c2962d8147380b00bb965c0d42b7e05ca4596868. After
discussion
in refs #28718, the decision is to treat the reverted statements as bugs.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28718#comment:9>
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.ff81a71dabb98cc0db27a66f14b43dca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
