diff options
author | Matt McCutchen <matt@mattmccutchen.net> | 2016-11-14 13:20:24 -0500 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2016-11-14 11:23:07 -0800 |
commit | 235ec24352e151bed37063a004b9800ee0debd74 (patch) | |
tree | 6646f0e70a1cd42276ae6e3e4f863b2097146b69 /Documentation/gitnamespaces.txt | |
parent | 0b65a8dbdb38962e700ee16776a3042beb489060 (diff) | |
download | git-235ec24352e151bed37063a004b9800ee0debd74.tar.gz |
doc: mention transfer data leaks in more placesmm/push-social-engineering-attack-doc
The "SECURITY" section of the gitnamespaces(7) man page described two
ways for a client to steal data from a server that wasn't intended to be
shared. Similar attacks can be performed by a server on a client, so
adapt the section to cover both directions and add it to the
git-fetch(1), git-pull(1), and git-push(1) man pages. Also add
references to this section from the documentation of server
configuration options that attempt to control data leakage but may not
be fully effective.
Signed-off-by: Matt McCutchen <matt@mattmccutchen.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/gitnamespaces.txt')
-rw-r--r-- | Documentation/gitnamespaces.txt | 20 |
1 files changed, 1 insertions, 19 deletions
diff --git a/Documentation/gitnamespaces.txt b/Documentation/gitnamespaces.txt index 7685e3651a..b614969ad2 100644 --- a/Documentation/gitnamespaces.txt +++ b/Documentation/gitnamespaces.txt @@ -61,22 +61,4 @@ For a simple local test, you can use linkgit:git-remote-ext[1]: git clone ext::'git --namespace=foo %s /tmp/prefixed.git' ---------- -SECURITY --------- - -Anyone with access to any namespace within a repository can potentially -access objects from any other namespace stored in the same repository. -You can't directly say "give me object ABCD" if you don't have a ref to -it, but you can do some other sneaky things like: - -. Claiming to push ABCD, at which point the server will optimize out the - need for you to actually send it. Now you have a ref to ABCD and can - fetch it (claiming not to have it, of course). - -. Requesting other refs, claiming that you have ABCD, at which point the - server may generate deltas against ABCD. - -None of this causes a problem if you only host public repositories, or -if everyone who may read one namespace may also read everything in every -other namespace (for instance, if everyone in an organization has read -permission to every repository). +include::transfer-data-leaks.txt[] |