[docs] Warn that debug logging can expose passwords #17458
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When debug logging is enabled in Logstash, it may expose sensitive information such as passwords into the logs. Document this behavior.
|
hi @toby-sutor can you walk me through the setup you had? plain debug logging shouldn't do that: |
|
Thank you for checking. In my repro on 8.17.4 it is also correctly redacted. However, it was reported by a customer, and we had similar reports at #15530, so I thought it would be a good opportunity to document this potentially happening in general. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When debug logging is enabled in Logstash, it may expose sensitive information such as passwords into the logs. Document this behavior.
Logs