BigW Consortium Gitlab

Skip to content

G
gitlab-ce
Commit e8e2e8ca by Rémy Coutable
Options

Merge branch 'patch-18' into 'master'

clarify that only some Runner Executors have these security concerns See merge request !14068
parents a34555be a13402da
Showing with 4 additions and 2 deletions
doc/ci/runners/README.md
...@@ -228,7 +228,8 @@ To make a Runner pick tagged/untagged jobs: ...@@ -228,7 +228,8 @@ To make a Runner pick tagged/untagged jobs:
### Be careful with sensitive information ### Be careful with sensitive information
If you can run a job on a Runner, you can get access to any code it runs With some [Runner Executors](https://docs.gitlab.com/runner/executors/README.html),
if you can run a job on the Runner, you can get access to any code it runs
and get the token of the Runner. With shared Runners, this means that anyone and get the token of the Runner. With shared Runners, this means that anyone
that runs jobs on the Runner, can access anyone else's code that runs on the that runs jobs on the Runner, can access anyone else's code that runs on the
Runner. Runner.
...@@ -237,7 +238,8 @@ In addition, because you can get access to the Runner token, it is possible ...@@ -237,7 +238,8 @@ In addition, because you can get access to the Runner token, it is possible
to create a clone of a Runner and submit false jobs, for example. to create a clone of a Runner and submit false jobs, for example.
The above is easily avoided by restricting the usage of shared Runners The above is easily avoided by restricting the usage of shared Runners
on large public GitLab instances and controlling access to your GitLab instance. on large public GitLab instances, controlling access to your GitLab instance,
and using more secure [Runner Executors](https://docs.gitlab.com/runner/executors/README.html).
### Forks ### Forks
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment