| commit | 235ec24352e151bed37063a004b9800ee0debd74 | |
| author | Matt McCutchen <matt@mattmccutchen.net> | |
| Mon, 14 Nov 2016 18:20:24 +0000 (14 13:20 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 14 Nov 2016 19:23:07 +0000 (14 11:23 -0800) | ||
| tree | 6646f0e70a1cd42276ae6e3e4f863b2097146b69 | treesnapshot (tar.gz zip) |
| parent | 0b65a8dbdb38962e700ee16776a3042beb489060 | commitdiff |
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>
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>