We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
The SQL logger - enabled with log level trace - logs SQL statements and their values. This can lead to leakage of PII or other sensitive information to log files (see e.g. https://www.wired.com/story/facebook-passwords-plaintext-change-yours/) and should be removed.
The text was updated successfully, but these errors were encountered:
Should we only log on leak_sensitive_values or remove that completely?
leak_sensitive_values
Sorry, something went wrong.
Remove completely, we have Jaeger for real tracing :)
zepatrik
No branches or pull requests
Describe the bug
The SQL logger - enabled with log level trace - logs SQL statements and their values. This can lead to leakage of PII or other sensitive information to log files (see e.g. https://www.wired.com/story/facebook-passwords-plaintext-change-yours/) and should be removed.
The text was updated successfully, but these errors were encountered: