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

don't log full env when starting kernels fails #191

Merged
merged 1 commit into from Aug 31, 2016

Conversation

minrk
Copy link
Member

@minrk minrk commented Aug 26, 2016

since it could contain sensitive info like API keys.

PATH is included explicitly, but no other env is logged.

This does hide useful info like PYTHONPATH, locale, etc. but there is no way to maintain a safe language-agnostic env whitelist.

cc @jasongrout

closes jupyter/notebook#1714

since it could contain sensitive info like API keys.

PATH is included explicitly, but no other env is logged.

This does hide useful info like PYTHONPATH, locale, etc.
but there is no way to maintain a safe language-agnostic env whitelist.
@minrk
Copy link
Member Author

minrk commented Aug 26, 2016

Alternative: include env keys, but not values. However, one could argue that even the presence of certain keys should not be disclosed.

@takluyver takluyver added this to the 4.4 milestone Aug 26, 2016
@minrk minrk merged commit 2b7fe62 into jupyter:master Aug 31, 2016
@minrk minrk deleted the no-log-env branch August 31, 2016 08:39
@jasongrout
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

don't print full environment in error messages when starting a new kernel
3 participants