diff options
| author | Jan Provaznik <jprovaznik@gitlab.com> | 2017-12-10 10:02:50 +0100 |
|---|---|---|
| committer | Jan Provaznik <jprovaznik@gitlab.com> | 2017-12-12 16:59:40 +0100 |
| commit | e297c4175df7a3af12dfff5bb9947560ce8add17 (patch) | |
| tree | 65d19c8dc147003aa027486f849088b5184727c2 /doc/administration | |
| parent | d673628de003d1ce1402f03311066339828fb811 (diff) | |
| download | gitlab-ce-e297c4175df7a3af12dfff5bb9947560ce8add17.tar.gz | |
Fixed doc for create MR from emaildocs-jprovazn-create-from-email
* fixed anchor for create MR from email
* added a screenshot for this feature
Diffstat (limited to 'doc/administration')
| -rw-r--r-- | doc/administration/reply_by_email.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/administration/reply_by_email.md b/doc/administration/reply_by_email.md index 1304476e678..3a2cced37bf 100644 --- a/doc/administration/reply_by_email.md +++ b/doc/administration/reply_by_email.md @@ -89,9 +89,11 @@ email address in order to sign up. If you also host a public-facing GitLab instance at `hooli.com` and set your incoming email domain to `hooli.com`, an attacker could abuse the "Create new -issue by email" feature by using a project's unique address as the email when -signing up for Slack, which would send a confirmation email, which would create -a new issue on the project owned by the attacker, allowing them to click the +issue by email" or +"[Create new merge request by email](../user/project/merge_requests/index.md#create-new-merge-requests-by-email)" +features by using a project's unique address as the email when signing up for +Slack, which would send a confirmation email, which would create a new issue or +merge request on the project owned by the attacker, allowing them to click the confirmation link and validate their account on your company's private Slack instance. |