From: Fraser Tweedale <frase@frase.id.au>
To: git@vger.kernel.org
Cc: Fraser Tweedale <frase@frase.id.au>
Subject: [PATCH] documentation: add git transport security notice
Date: Wed, 26 Jun 2013 15:53:59 +1000 [thread overview]
Message-ID: <1372226039-31689-1-git-send-email-frase@frase.id.au> (raw)
The fact that the git transport does not do any 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 <frase@frase.id.au>
---
Documentation/urls.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/urls.txt b/Documentation/urls.txt
index 3ca122f..b58a647 100644
--- a/Documentation/urls.txt
+++ b/Documentation/urls.txt
@@ -11,6 +11,9 @@ and ftps can be used for fetching and rsync can be used for fetching
and pushing, but these are inefficient and deprecated; do not use
them).
+The git transport does not do any authentication and should be used
+with caution on unsecured networks.
+
The following syntaxes may be used with them:
- ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/
--
1.8.3.1
next reply other threads:[~2013-06-26 5:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 5:53 Fraser Tweedale [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-05 8:41 [PATCH] documentation: add git transport security notice Fraser Tweedale
2013-07-07 0:50 ` Jonathan Nieder
2013-06-24 10:23 Fraser Tweedale
2013-06-24 16:24 ` Junio C Hamano
2013-06-24 21:57 ` Fraser Tweedale
2013-06-24 22:27 ` Fredrik Gustafsson
2013-06-24 22:35 ` Junio C Hamano
2013-06-24 22:47 ` Fredrik Gustafsson
2013-06-24 22:28 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1372226039-31689-1-git-send-email-frase@frase.id.au \
--to=frase@frase.id.au \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).