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

Run Actions for all contributions #65

Open
iainelder opened this issue Mar 16, 2023 · 0 comments
Open

Run Actions for all contributions #65

iainelder opened this issue Mar 16, 2023 · 0 comments

Comments

@iainelder
Copy link
Collaborator

Last week's PR #64 had a bit of back-and-forth because of delayed CI feedback to a new contributor.

Dave explained that we currently err on the side of safety over convenience

To avoid being able to hijack Actions, they only run for commits directly to this repo by maintainers. Otherwise someone could fork and cat out the deploy token for pypi :)

I'd like to find a way to improve the CI experience for all contributors without compromising the project's safety.

Today I learned that there is a name for the threat: Poisoned Pipeline Execution.

Omer Gil of Cider Security has a good write up of the threat and some recommendations for how to handle it, including how to handle access to secrets.

I don't remember where I first read about the problem or potential solutions, but it's clearly a common one. There may be some existing solutions for Github actions that we can reuse.

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

No branches or pull requests

1 participant