-
Notifications
You must be signed in to change notification settings - Fork 38
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
fatal error compromises the token #7
Comments
@MoOx, which build number should i be looking at? |
Oh shit, travis didn't update the link. Let me take a look so I can find the build |
Well to reproduce, juste use an incorrect repo url like |
So here is an output
(don't worry this token is dead) |
Cool, thanks for the example. I actually have been able to reproduce the issue already, and I'm working on a solution to filter the output of the commands that use $repo. I just haven't had the time to finish it. I'll let you know. |
Awesome ! |
@X1011 Any ETA on this? |
@isiahmeadows unfortunately, no; i have an idea for a solution, and i started implementing it, but i haven't had time to finish it. |
The script we were using has a fairly sigificant security issue (X1011/git-directory-deploy#7) that could expose the access token used to push the documentation.
@X1011 Could you, maybe, outline your idea here so that contributors could pick this up? Or, in case you think it isn't an exhaustive solution, consumers could apply it on their own forks. |
see it by yourself https://travis-ci.org/putaindecode/putaindecode.fr#L8587
Any idea how to catch this to avoid the token to be compromised ?
The text was updated successfully, but these errors were encountered: