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

ANACONDA_TOKEN exposed in travis ci build #2601

Closed
rlee287 opened this issue Jun 5, 2016 · 2 comments
Closed

ANACONDA_TOKEN exposed in travis ci build #2601

rlee287 opened this issue Jun 5, 2016 · 2 comments
Labels
locked [bot] locked due to inactivity

Comments

@rlee287
Copy link

rlee287 commented Jun 5, 2016

In .travis.yml, special care is taken to avoid exposing the value of ANACONDA_TOKEN. However, the printenv command exposes this value in plaintext (see line 199 of this travis log.) As a suggestion, printenv could be replaced with something like this (note: have not verified sed expression yet):

printenv | sed -e 's/ANACONDA_TOKEN=*/ANACONDA_TOKEN=[secured]' > env.txt; cat env.txt; rm env.txt

Moreover, the exposed token needs to be revoked and replaced with a new one.

@kalefranz
Copy link
Contributor

kalefranz commented May 6, 2017

I don't know of any instance of 'printenv' existing in the conda code base. Nor does conda itself do anything with ANACONDA_TOKEN.

@github-actions
Copy link

Hi there, thank you for your contribution to Conda!

This issue has been automatically locked since it has not had recent activity after it was closed.

Please open a new issue if needed.

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Oct 18, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity
Projects
None yet
Development

No branches or pull requests

2 participants