oslo.log's "debug" option was co-opted to also indicate that the
responses should include more information. A separate config
option should be used instead so that deployers don't mistakenly
expose themselves to security issues.
The debug option still is used for what it does in oslo.log and
how it works on all other projects -- if you're not using a log
config file it sets the base logger to debug.
Reviewed: https:/ /review. openstack. org/207226 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=2afad4dc30c d1e210f2353ce98 7fe1bbdd8b93d7
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2afad4dc30cd1e2 10f2353ce987fe1 bbdd8b93d7
Author: Brant Knudson <email address hidden>
Date: Wed Jul 29 16:29:42 2015 -0500
Config option for insecure responses
oslo.log's "debug" option was co-opted to also indicate that the
responses should include more information. A separate config
option should be used instead so that deployers don't mistakenly
expose themselves to security issues.
The debug option still is used for what it does in oslo.log and
how it works on all other projects -- if you're not using a log
config file it sets the base logger to debug.
SecurityImpact
Change-Id: Icf8dd2f0b88abc 89092d487bbcefb 525960c4ec6
Closes-Bug: 1479523