Skip to content
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

Scrub API Keys from Logs #42

Closed
pearkes opened this issue Jun 20, 2013 · 3 comments · Fixed by #58
Closed

Scrub API Keys from Logs #42

pearkes opened this issue Jun 20, 2013 · 3 comments · Fixed by #58

Comments

@pearkes
Copy link
Collaborator

pearkes commented Jun 20, 2013

We should replace them with something innocuous. As we're just falling back to Faraday's logging, I'm not sure if this is possible or how we might do it.

@petems
Copy link
Owner

petems commented Jul 12, 2013

I'm having a stab at this, I'm trying to figure out where on the stack I should put it?

I've got a working middleware version for faraday
https://github.com/petems/faraday-scrublogs

Or it could be done it on faraday itself?

Or it could be done on digital_ocean? Hmm....

@pearkes
Copy link
Collaborator Author

pearkes commented Jul 12, 2013

I would say it would be cool if it could be done upstream on digital_ocean, as it seems like a relatively worthwhile feature.

@rmoriz hope you don't mind a ping, do you have an opinion on this type of thing? We're seeing a slight security concern with users pasting debug logs generated with the debug flag for the digital_ocean gem turned on, as it dumps HTTP URLs with access_tokens/client_ids visible.

The only issue I see with upstream is how do you configure it to scrub / not scrub. Sometimes it would be worthwhile to get raw output. Perhaps we should just do it on our side.

@petems
Copy link
Owner

petems commented Jul 12, 2013

I opened a PR on faraday with an implementation: lostisland/faraday#286 😸

petems added a commit that referenced this issue Aug 6, 2013
Means we can fix issues such as #53 and #42 without having to wait for
upstream changes on faraday itself and digital_ocean
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants