Skip to content

Commit 2061801

Browse files
frasertweedalegitster
authored andcommitted
documentation: add git:// transport security notice
The fact that the git:// transport does no authentication is easily overlooked. For example, DNS poisoning may result in fetching from somewhere that was not intended. Add a brief security notice to the "GIT URLS" section of the documentation stating that the git transport should be used with caution on unsecured networks. Signed-off-by: Fraser Tweedale <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent c0add30 commit 2061801

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

Documentation/urls.txt

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,9 @@ and ftps can be used for fetching and rsync can be used for fetching
1111
and pushing, but these are inefficient and deprecated; do not use
1212
them).
1313

14+
The native transport (i.e. git:// URL) does no authentication and
15+
should be used with caution on unsecured networks.
16+
1417
The following syntaxes may be used with them:
1518

1619
- ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/

0 commit comments

Comments
 (0)