PyKMIP/kmip/core
Tim Burke f60bae83d0 Secure logging by default
As an application developer, you might expect to be able to turn on
debug logging at the root logger with something like

    logging.basicConfig(level=logging.DEBUG)

However, if the application needed to fetch any secrets from a KMIP
server, these previously would be logged as part of the wire protocol.
Further, any passwords in configs would also get logged at DEBUG.
Applications would need to proactively silence such logging, as in
https://github.com/openstack/swift/commit/12b6d46

Now, we will default the logger level to INFO to suppress the debug
logging. However, seeing the on-wire data may still be useful, for
example when developing a new KMIP server. So, allow developers to
consciously set the logger level to DEBUG.
2018-10-09 14:24:22 -07:00
..
factories Add Check support to the payload factories 2018-04-17 00:32:20 -04:00
messages Add the request and response payloads for the Rekey operation 2018-04-12 22:34:58 -04:00
__init__.py PyKMIP - Release v0.0.1 2014-08-13 19:23:05 -04:00
attributes.py Remove unused error code 2017-12-07 20:59:23 -05:00
config_helper.py Secure logging by default 2018-10-09 14:24:22 -07:00
enums.py Rename the CertificateTypeEnum enum to CertificateType 2017-10-11 08:24:55 -04:00
exceptions.py Integrate policy file monitoring with the server 2018-04-11 13:42:44 -04:00
misc.py Updating support for the Enumeration primitive 2015-09-29 13:23:44 -04:00
objects.py Add a better error message when reading unparseable attributes 2018-05-17 13:28:11 -04:00
policy.py Rename the 'default' policy section to 'preset' 2018-05-17 13:55:50 -04:00
primitives.py Remove unused error code 2017-12-07 20:59:23 -05:00
secrets.py Rename the CertificateTypeEnum enum to CertificateType 2017-10-11 08:24:55 -04:00
utils.py Remove unused error code 2017-12-07 20:59:23 -05:00