git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>,
	Fraser Tweedale <frase@frase.id.au>,
	git@vger.kernel.org
Subject: Re: [PATCH] documentation: add git transport security notice
Date: Tue, 25 Jun 2013 00:47:08 +0200	[thread overview]
Message-ID: <20130624224708.GB32270@paksenarrion.iveqy.com> (raw)
In-Reply-To: <7vtxkn5e8o.fsf@alter.siamese.dyndns.org>

On Mon, Jun 24, 2013 at 03:35:19PM -0700, Junio C Hamano wrote:
> > I don't understand this. How is git:// insecure?
> 
> If your DNS is poisoned, or your router is compromised to allow your
> traffic diverted, you may be fetching from somewhere you did not
> intend to.  As I explained in a separate message, that does not
> necessarily result in your repository corrupting, but the result,
> even though it may be "git fsck" clean at the bit level, needs
> additional validation measure, such as signed tags, to be safely
> used to base your further work on top.

Thanks for the explanation. Of course you need to verify your latest
commit sha1 against a trustworthy source. That would be enough to
prevent this scenario, yes?

If we add warnings for git:// should we also add warnings for
http://? Or do we consider that common knowledge?

-- 
Med vänliga hälsningar
Fredrik Gustafsson

tel: 0733-608274
e-post: iveqy@iveqy.com

  reply	other threads:[~2013-06-24 22:47 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
2013-06-24 22:35       ` Junio C Hamano
2013-06-24 22:47         ` Fredrik Gustafsson [this message]
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

  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=20130624224708.GB32270@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. 
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).