From ec60358d52be0dc99f52db94dc95209f1486eac9 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Tue, 1 Oct 2019 03:05:57 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/user/admin_area/settings/visibility_and_access_controls.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/user/admin_area/settings/visibility_and_access_controls.md') diff --git a/doc/user/admin_area/settings/visibility_and_access_controls.md b/doc/user/admin_area/settings/visibility_and_access_controls.md index e07e5f54ada..81e09e4bb8a 100644 --- a/doc/user/admin_area/settings/visibility_and_access_controls.md +++ b/doc/user/admin_area/settings/visibility_and_access_controls.md @@ -105,7 +105,7 @@ With GitLab's access restrictions, you can select with which protocols users can GitLab. Disabling an access protocol does not block access to the server itself via those ports. The ports -used for the protocol, SSH or HTTP, will still be accessible. The GitLab restrictions apply at the +used for the protocol, SSH or HTTP(S), will still be accessible. The GitLab restrictions apply at the application level. To specify the enabled Git access protocols: @@ -150,7 +150,7 @@ For more details, see [SSH key restrictions](../../../security/ssh_keys_restrict > [Introduced](https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3586) in GitLab 10.3. -This option is enabled by default. By disabling it, both pull and push mirroring will no longer +This option is enabled by default. By disabling it, both [pull and push mirroring](../../../workflow/repository_mirroring.md) will no longer work in every repository and can only be re-enabled by an admin on a per-project basis. ![Mirror settings](img/mirror_settings.png) -- cgit v1.2.1