summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRémy Coutable <remy@rymai.me>2017-09-08 10:53:28 +0000
committerRémy Coutable <remy@rymai.me>2017-09-08 10:53:28 +0000
commite8e2e8ca9790e47cf22569aa4d97b01937ea83ec (patch)
tree08914b87ca5c78b47f2754d3d61f8232c3c23715
parenta34555be19e2956bfe6e2902433c1621f801cbe4 (diff)
parenta13402da2555292f33f22993b840e60b3f260e66 (diff)
downloadgitlab-ce-e8e2e8ca9790e47cf22569aa4d97b01937ea83ec.tar.gz
Merge branch 'patch-18' into 'master'
clarify that only some Runner Executors have these security concerns See merge request !14068
-rw-r--r--doc/ci/runners/README.md6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/ci/runners/README.md b/doc/ci/runners/README.md
index f5d3b524d6e..bac8e972754 100644
--- a/doc/ci/runners/README.md
+++ b/doc/ci/runners/README.md
@@ -228,7 +228,8 @@ To make a Runner pick tagged/untagged jobs:
### 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
that runs jobs on the Runner, can access anyone else's code that runs on the
Runner.
@@ -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.
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