summaryrefslogtreecommitdiff
path: root/Documentation/git-push.txt
diff options
context:
space:
mode:
authorMatt McCutchen <matt@mattmccutchen.net>2016-11-14 18:20:24 (GMT)
committerJunio C Hamano <gitster@pobox.com>2016-11-14 19:23:07 (GMT)
commit235ec24352e151bed37063a004b9800ee0debd74 (patch)
tree6646f0e70a1cd42276ae6e3e4f863b2097146b69 /Documentation/git-push.txt
parent0b65a8dbdb38962e700ee16776a3042beb489060 (diff)
downloadgit-235ec24352e151bed37063a004b9800ee0debd74.zip
git-235ec24352e151bed37063a004b9800ee0debd74.tar.gz
git-235ec24352e151bed37063a004b9800ee0debd74.tar.bz2
doc: mention transfer data leaks in more places
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/git-push.txt')
-rw-r--r--Documentation/git-push.txt2
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt
index cf6ee4a..8234136 100644
--- a/Documentation/git-push.txt
+++ b/Documentation/git-push.txt
@@ -552,6 +552,8 @@ Commits A and B would no longer belong to a branch with a symbolic name,
and so would be unreachable. As such, these commits would be removed by
a `git gc` command on the origin repository.
+include::transfer-data-leaks.txt[]
+
GIT
---
Part of the linkgit:git[1] suite