Warn when logging severity is excessive
Logging at debug
or trace
is risky, since it can expose information that would be useful to an attacker. We should warn when these severities are in use.
See also #550 and #551 (closed).
Logging at debug
or trace
is risky, since it can expose information that would be useful to an attacker. We should warn when these severities are in use.
See also #550 and #551 (closed).
added Security label
mentioned in merge request !687 (merged)
mentioned in issue #514 (closed)
changed milestone to %Arti: Feature parity with the C implementation
added Roadmap::Future label
added Client Parity: MUST label
changed time estimate to 8h
removed milestone %Arti: Feature parity with the C implementation
added Client Parity label and removed Client Parity: MUST label