path: root/Documentation/git-pull.txt
diff options
authorMatt McCutchen <>2016-11-14 18:20:24 (GMT)
committerJunio C Hamano <>2016-11-14 19:23:07 (GMT)
commit235ec24352e151bed37063a004b9800ee0debd74 (patch)
tree6646f0e70a1cd42276ae6e3e4f863b2097146b69 /Documentation/git-pull.txt
parent0b65a8dbdb38962e700ee16776a3042beb489060 (diff)
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 <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-pull.txt')
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index a62a2a6..0773c84 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -228,6 +228,8 @@ If you tried a pull which resulted in complex conflicts and
would want to start over, you can recover with 'git reset'.
Using --recurse-submodules can only fetch new commits in already checked