diff options
Diffstat (limited to 'data/deprecations/14-5-disable_strict_host_key_checking.yml')
| -rw-r--r-- | data/deprecations/14-5-disable_strict_host_key_checking.yml | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/data/deprecations/14-5-disable_strict_host_key_checking.yml b/data/deprecations/14-5-disable_strict_host_key_checking.yml new file mode 100644 index 00000000000..a3a6a3bf223 --- /dev/null +++ b/data/deprecations/14-5-disable_strict_host_key_checking.yml @@ -0,0 +1,14 @@ +- name: "Known host required for GitLab Runner SSH executor" + announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated. + announcement_date: "2021-11-22" + removal_milestone: "15.0" # the milestone when this feature is planned to be removed + removal_date: "2022-05-22" + breaking_change: true + body: | # Do not modify this line, instead modify the lines below. + In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner `config.toml` file. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor. + + In GitLab 15.0 and later, the default value for this configuration option will change from `true` to `false`. This means that strict host key checking will be enforced when using the GitLab Runner SSH executor. + stage: Verify + tiers: [Core, Premium, Ultimate] + issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28192 + documentation_url: https://docs.gitlab.com/runner/executors/ssh.html#security |