Skip to content

Verbose logging without exposing passwords #1704

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

Closed
all-iver opened this issue May 4, 2016 · 4 comments
Closed

Verbose logging without exposing passwords #1704

all-iver opened this issue May 4, 2016 · 4 comments
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@all-iver
Copy link

all-iver commented May 4, 2016

Environment Setup

Elastic beanstalk.

Steps to reproduce

Enable verbose logging via environment variables.

Logs/Trace

verbose: GET /parse/login { host: 'xxx',
...
'content-type': 'text/plain',
'user-agent': 'node-XMLHttpRequest, Parse/js1.8.3 (NodeJS 4.3.0)',
"username": "[email protected]",
"password": "plain-text-password"
}

Apologies if this is not a Parse specific question, but what are my options for logging? I see that I can enable VERBOSE=1 in my environment settings, but when I do that I see log statements with passwords in plain text like the above. I'd like to avoid having passwords logged like this. I'm not positive that log is actually coming from Parse, but it is formatted like the other Parse messages so I'm assuming it is?

@drew-gross
Copy link
Contributor

We should probably censor the password in logs, like rails does.

@drew-gross drew-gross added the type:bug Impaired feature or lacking behavior that is likely assumed label May 6, 2016
@flovilmart
Copy link
Contributor

@drew-gross good point.

@drew-gross
Copy link
Contributor

Fixed in #1790

@sirnacnud
Copy link

sirnacnud commented Aug 14, 2016

This issue still isn't fixed as of 2.2.17. When a user logs in, the password is still getting logged. I did some debugging and looks like the problem is that maskSensitiveBody() in PromiseRouter.js doesn't check for a GET request on /parse/login, as the request body contains the username and password.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

4 participants