Skip to content
代码片段 群组 项目
未验证 提交 15792b96 编辑于 作者: Zachary Painter's avatar Zachary Painter 提交者: GitLab
浏览文件

Merge branch 'docs-vmihai-master-patch-43617' into 'master'

Clarify security implications for deleted users

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/184091



Merged-by: default avatarZachary Painter <zpainter@gitlab.com>
Approved-by: default avatarZachary Painter <zpainter@gitlab.com>
Reviewed-by: default avatarZachary Painter <zpainter@gitlab.com>
Co-authored-by: default avatarVlad Mihai <vmihai@gitlab.com>
No related branches found
No related tags found
2 合并请求!3031Merge per-main-jh to main-jh by luzhiyuan,!3030Merge per-main-jh to main-jh
......@@ -70,7 +70,7 @@ In addition:
- Gains access to the protected branch, as well as to the deploy key itself.
- Can push to the protected branch, if the deploy key has read-write permission.
This is true even if the branch is protected against changes from all users.
- Deploy keys are invalidated when the user is blocked or removed from the instance.
- If the creator of the deploy key is blocked or removed from the instance, the user can still pull changes from the group or project, but not push.
As with all sensitive information, you should ensure only those who need access to the secret can read it.
For human interactions, use credentials tied to users such as personal access tokens.
......
0% 加载中 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册