-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Obfuscate password name value pairs in log strings #2755
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
Obfuscate password name value pairs in log strings #2755
Conversation
@flovilmart updated the pull request - view changes |
35b1549
to
d106588
Compare
@flovilmart updated the pull request - view changes |
@flovilmart oh, now i see what you mean in #2680 (comment) I think that what you're suggesting is trying something like:
and remove cleaning from the client's responsibility. I like it and will take a look, but can't get to tonight...will need to take a look at what comes into ...args :) |
No problem, there's no rush :) |
LGTM |
Alright let's merge that so it's available on the latest branch, we'll refactor later |
Move password masking functionality into LoggerController. The is a more aggresive approach to masking password string in the logs. Cleaning the url is still in the PromiseRouter because picking it out of the log string would be fragile. This will cause more log messages to be scanned for password strings, and may cause a password string to be obsfucated that is not neccesarily part of parse internals -- but i think that is still a good thing.... see: parse-community#2755 & parse-community#2680
Move password masking functionality into LoggerController. The is a more aggresive approach to masking password string in the logs. Cleaning the url is still in the PromiseRouter because picking it out of the log string would be fragile. This will cause more log messages to be scanned for password strings, and may cause a password string to be obsfucated that is not neccesarily part of parse internals -- but i think that is still a good thing.... see: #2755 & #2680
fixes: #2680