Skip to content
Browse files

Fixed #13624: added SIGNATURE to the list of settings to hide on debu…

…g pages.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 3180f93 commit 2311bcbd016783d20a64b0b4d745318af0a1c0dd @jacobian jacobian committed
Showing with 4 additions and 3 deletions.
  1. +1 −1  django/views/
  2. +3 −2 docs/ref/settings.txt
2  django/views/
@@ -12,7 +12,7 @@
from django.utils.encoding import smart_unicode, smart_str
def linebreak_iter(template_source):
yield 0
5 docs/ref/settings.txt
@@ -494,8 +494,9 @@ A boolean that turns on/off debug mode.
If you define custom settings, `django/views/`_ has a ``HIDDEN_SETTINGS``
regular expression which will hide from the DEBUG view anything that contains
-``'SECRET'``, ``'PASSWORD'``, or ``'PROFANITIES'``. This allows untrusted users to
-be able to give backtraces without seeing sensitive (or offensive) settings.
+``'SECRET'``, ``'PASSWORD'``, ``'PROFANITIES'``, or ``'SIGNATURE'``. This allows
+untrusted users to be able to give backtraces without seeing sensitive (or
+offensive) settings.
Still, note that there are always going to be sections of your debug output that
are inappropriate for public consumption. File paths, configuration options, and

0 comments on commit 2311bcb

Please sign in to comment.
Something went wrong with that request. Please try again.