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

Add self-hosted runner to deploy new software on hardware #40

Open
payano opened this issue May 12, 2020 · 1 comment
Open

Add self-hosted runner to deploy new software on hardware #40

payano opened this issue May 12, 2020 · 1 comment

Comments

@payano
Copy link
Owner

payano commented May 12, 2020

https://help.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories

Under settings->actions->add-new-runner

@payano
Copy link
Owner Author

payano commented May 12, 2020

Self-hosted runner security with public repositories

We recommend that you do not use self-hosted runners with public repositories.

Forks of your public repository can potentially run dangerous code on your self-hosted runner machine by creating a pull request that executes the code in a workflow.

This is not an issue with GitHub-hosted runners because each GitHub-hosted runner is always a clean isolated virtual machine, and it is destroyed at the end of the job execution.

Untrusted workflows running on your self-hosted runner poses significant security risks for your machine and network environment, especially if your machine persists its environment between jobs. Some of the risks include:

Malicious programs running on the machine.
Escaping the machine's runner sandbox.
Exposing access to the machine's network environment.
Persisting unwanted or dangerous data on the machine.

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