#27518: HTTP Referer leaks password reset link
----------------------------------+--------------------------------------
Reporter: Romain Garrigues | Owner: nobody
Type: New feature | Status: new
Component: contrib.auth | Version: 1.10
Severity: Normal | Resolution:
Keywords: password reset | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by Romain Garrigues):
I also tried the second approach proposed in the article:
1/ check the token,
2/ generate a new one by changing the user password, making the old one
invalid (as the token is based mainly on user password and last_joined
fields),
3/ store it in the session,
4/ use this newly generated one for password reset confirmation.
It has the benefit of being almost backward compatible (I think), except
that, as we change the user password, if the user remember the password
when he access the form, quit the page and wants to login, he won't be
able to do it anymore.
On the other hand, he was in the process of resetting it, so it doesn't
seem critical to generate a random password at the meantime, and he can
still reset it anyway.
--
Ticket URL: <https://code.djangoproject.com/ticket/27518#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/064.4d3cd9bf00eb48f98f35b54b32756f3a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
