#29863: Allow configuration/customization of sensitive settings sanitization for
error emails
---------------------------------+--------------------------------------
Reporter: Daniel Harding | Owner: (none)
Type: New feature | Status: new
Component: Error reporting | Version: 2.1
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):
I'm not immediately convinced.
[https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-DEBUG The
documentation] explains, that settings including 'API', 'KEY', 'PASS',
'SECRET', 'SIGNATURE', and 'TOKEN' will be excluded. I think taking no
action here and promoting the choose of appropriate names may be better.
In the case of third-party apps, for example, we don't want to the app to
choose setting names that won't be excluded by default and have to say,
"don't forget to customize error reporting for better security."
--
Ticket URL: <https://code.djangoproject.com/ticket/29863#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/067.3b5ffdf1afc414dd63c78ddd9670ccc7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
