Commit 302b0ec2 authored by Amy Qualls's avatar Amy Qualls

Merge branch 'docs-id-self-signed-cert' into 'master'

Deprecate Gitlab Shell's self_signed_cert setting

See merge request gitlab-org/gitlab!78078
parents a5caed42 4374e035
...@@ -1041,9 +1041,8 @@ To use GitLab with HTTPS: ...@@ -1041,9 +1041,8 @@ To use GitLab with HTTPS:
1. Update `ssl_certificate` and `ssl_certificate_key`. 1. Update `ssl_certificate` and `ssl_certificate_key`.
1. Review the configuration file and consider applying other security and performance enhancing features. 1. Review the configuration file and consider applying other security and performance enhancing features.
Using a self-signed certificate is discouraged but if you must use it, follow the normal directions. Then: Using a self-signed certificate is discouraged. If you must use one,
follow the normal directions and generate a self-signed SSL certificate:
1. Generate a self-signed SSL certificate:
```shell ```shell
mkdir -p /etc/nginx/ssl/ mkdir -p /etc/nginx/ssl/
...@@ -1052,7 +1051,12 @@ Using a self-signed certificate is discouraged but if you must use it, follow th ...@@ -1052,7 +1051,12 @@ Using a self-signed certificate is discouraged but if you must use it, follow th
sudo chmod o-r gitlab.key sudo chmod o-r gitlab.key
``` ```
1. In the `config.yml` of GitLab Shell set `self_signed_cert` to `true`. WARNING:
The `self_signed_cert` variable is
[deprecated and redundant](https://gitlab.com/gitlab-org/gitlab-shell/-/issues/120).
It is set to `false` by default, but still accepts self-signed certificates. Setting
this value to `true` allows any certificate to be accepted, and can make
machine-in-the-middle attacks possible.
### Enable Reply by email ### Enable Reply by email
......
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