-
-
Notifications
You must be signed in to change notification settings - Fork 395
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
[Important] Limit secret access to plugins only #1071
Comments
I don't see how this could protect secrets? You could just create a plugin (normal docker image) that leaks the secrets, couldn't you? |
this could be helpful in combination with trusted images ex. currently setting trusted image image: woodpeckerci/plugin-git
commands:
- echo ${SECRET} adding such option would prevent that |
-> it's a trusted image I dont like to go more into details what else you could do ... - but It's a open risk (if repo is not gated)! |
bounty: 50$ |
similar to the images filter for secrets, add a checkbox to only inject secret if step is exec as plugin.
this ensure only the intended entry-point do get the secrets to handle.
this does help if a plugin is not based from scratch image but do contain an shell that could be used.
bounty: 50$
The text was updated successfully, but these errors were encountered: