summaryrefslogtreecommitdiff
path: root/doc/security
diff options
context:
space:
mode:
authorSytse Sijbrandij <sytses@gmail.com>2014-09-18 09:44:12 +0200
committerSytse Sijbrandij <sytses@gmail.com>2014-09-18 09:44:12 +0200
commit664b433afef12b12d93fac078826ad6fc7c492f5 (patch)
treedb4fde3596709fd68699158e52f3460627f75bb0 /doc/security
parentff4a45effb49b5935ba46ca0f17221062bd28d52 (diff)
downloadgitlab-ce-664b433afef12b12d93fac078826ad6fc7c492f5.tar.gz
Add explanation about unintentional sharing.
Diffstat (limited to 'doc/security')
-rw-r--r--doc/security/information_exclusivity.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/security/information_exclusivity.md b/doc/security/information_exclusivity.md
index f6f89ce58a9..127166ae2e7 100644
--- a/doc/security/information_exclusivity.md
+++ b/doc/security/information_exclusivity.md
@@ -6,3 +6,4 @@ In GitLab every project member that is not a guest (so reporters, developers and
After obtaining this local copy the user can upload the full repository anywhere, including another project under their control or another server.
The consequense is that you can't build access controls that prevent the intentional sharing of source code by users that have access to the source code.
This is an inherent feature of a DVCS and all git management systems have this limitation.
+Obviously you can take steps to prevent unintentional sharing and information destruction, this is why only some people are allowed to invite others and nobody can force push a protected branch.