From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Fraser Tweedale <frase@frase.id.au>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] documentation: add git transport security notice
Date: Tue, 25 Jun 2013 00:27:03 +0200 [thread overview]
Message-ID: <20130624222703.GA32270@paksenarrion.iveqy.com> (raw)
In-Reply-To: <20130624215733.GU2457@bacardi.hollandpark.frase.id.au>
On Tue, Jun 25, 2013 at 07:57:35AM +1000, Fraser Tweedale wrote:
> The git transport is insecure and should be used with caution on
> unsecured networks.
I don't understand this. How is git:// insecure?
It's protocol with no authentication, because it's a protocol used for
public sharing.
The only point of encrypt git:// would be to verify that the recieved
data has not been altered along the way. However you can always trust
that the end result is an valid copy of the remote.
To me that means that it's as secure as a non-authentication protocoll
needs to be.
How would an "evil network" be able to do any harm to a git transport
over git://?
--
Med vänliga hälsningar
Fredrik Gustafsson
tel: 0733-608274
e-post: iveqy@iveqy.com
next prev parent reply other threads:[~2013-06-24 22:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 10:23 [PATCH] documentation: add git transport security notice Fraser Tweedale
2013-06-24 16:24 ` Junio C Hamano
2013-06-24 21:57 ` Fraser Tweedale
2013-06-24 22:27 ` Fredrik Gustafsson [this message]
2013-06-24 22:35 ` Junio C Hamano
2013-06-24 22:47 ` Fredrik Gustafsson
2013-06-24 22:28 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2013-06-26 5:53 Fraser Tweedale
2013-07-05 8:41 Fraser Tweedale
2013-07-07 0:50 ` Jonathan Nieder
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130624222703.GA32270@paksenarrion.iveqy.com \
--to=iveqy@iveqy.com \
--cc=frase@frase.id.au \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
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 NNTP newsgroup(s).