#24587: predictable CSRF functionality
------------------------------+--------------------------------------
Reporter: introvertmac | Owner: nobody
Type: Bug | Status: closed
Component: CSRF | Version: 1.7
Severity: Normal | Resolution: invalid
Keywords: CSRF | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by apollo13):
* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
As said on twitter and hackerone: Using Firebug to change your CSRF token
and cookie is not a security issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/24587#comment:1>
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/070.8368d712e6523aaad93c5ba7fbe5bcd4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
