#28215: sensitive_post_parameters/sensitive_variables leaking sensitive values
into
the http 500 exception email
---------------------------------+--------------------------------------
Reporter: Peter Zsoldos | Owner: (none)
Type: Bug | Status: new
Component: Error reporting | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by Tim Graham):
It would be helpful to give a high level overview of the issue in the
ticket's summary and description. The current summary is rather general
and the description doesn't detail the cause in much detail. Currently, I
have to open the sample project, unzip it, and read the code to try to
understand the issue.
If I'm reading it correctly, it looks like this particular case could be
fixed by marking `credentials` as a sensitive variable in
`contrib.auth.authenticate()` -- is that correct?
--
Ticket URL: <https://code.djangoproject.com/ticket/28215#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.bf2597f34f92a9e72f712a0dc3209042%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
