#19758: Password reset form should not leak information
------------------------------+------------------------------------
Reporter: anonymous | Owner: zerok
Type: Bug | Status: assigned
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: sprint2013 | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
------------------------------+------------------------------------
Changes (by zerok):
* owner: nobody => zerok
* status: new => assigned
* keywords: => sprint2013
Comment:
@carljm so you basically want to have the default behaviour to be the
"secure" approach and perhaps offer a setting (either globally or on a
per-form level) to switch to a version that exposes the existence of a
user's email?
--
Ticket URL: <https://code.djangoproject.com/ticket/19758#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
