-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
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
[0.9.3] InfluxDB log password redaction leaves query mangled, but not redacted #3883
Milestone
Comments
Does this still exist and how can we reproduce this issue? |
This issue still exists and needs to be fixed. The HTTP response logger simply replaces any strings in the query params that match the password right now. This exposes info about the password value itself and can lead to the situation above, where the password is set as a space. |
jsternberg
added a commit
that referenced
this issue
Apr 19, 2016
Sanitizing is now done through pattern matching rather than parsing the query and replacing the password in the query. This prevents accidentally redacting the wrong part of a query and revealing what the password is through association. Fixes #3883.
jsternberg
added a commit
that referenced
this issue
Apr 22, 2016
Sanitizing is now done through pattern matching rather than parsing the query and replacing the password in the query. This prevents accidentally redacting the wrong part of a query and revealing what the password is through association. Fixes #3883.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Password redaction isn't quite doing its job:
Which is something like
'[REDACTED]'.join("q=CREATE+USER+reader+WITH+PASSWORD+[etc]")
Not quite what you had in mind, I imagine. ;-)
The text was updated successfully, but these errors were encountered: