diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-18 03:07:45 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-18 03:07:45 +0300 |
commit | 7c077d960393e14b56d43cceaa7f609c703ac55f (patch) | |
tree | c3a5d79554b9be1d7434c8e9a8fcae35ab64af32 /doc/ci/runners | |
parent | da35510cdad8f8d3cb6c119682dc2735531983cd (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/runners')
-rw-r--r-- | doc/ci/runners/README.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/ci/runners/README.md b/doc/ci/runners/README.md index f7d1a3e88a2..4011ae4df70 100644 --- a/doc/ci/runners/README.md +++ b/doc/ci/runners/README.md @@ -365,8 +365,8 @@ We're always looking for contributions that can mitigate these ### Resetting the registration token for a Project If you think that registration token for a Project was revealed, you should -reset them. It's recommended because such token can be used to register another -Runner to the Project. It may be next used to obtain the values of secret +reset them. It's recommended because such a token can be used to register another +Runner to the Project. It may then be used to obtain the values of secret variables or clone the project code, that normally may be unavailable for the attacker. @@ -379,10 +379,10 @@ To reset the token: 1. After the page is refreshed, expand the **Runners settings** section and check the registration token - it should be changed. -From now on the old token is not valid anymore and will not allow to register -a new Runner to the project. If you are using any tools to provision and -register new Runners, you should now update the token that is used to the -new value. +From now on the old token is no longer valid and will not register +any new Runners to the project. If you are using any tools to provision and +register new Runners, the tokens used in those tools should be updated to reflect the +value of the new token. ## Determining the IP address of a Runner |