From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: Killing plaintext git:// in favor of https:// cloning
Date: Tue, 23 Feb 2016 06:05:12 +0100 [thread overview]
Message-ID: <CAHmME9phkpYxS8sSPqwULUtUmtrMeNGhjTdQQJQ_AoonMuNwPA@mail.gmail.com> (raw)
In-Reply-To: <20160222204309.0C53882322@gnosis.slac.com>
On Mon, Feb 22, 2016 at 9:43 PM, Joe Anakata
<jea-signup-cgit at anakata.org> wrote:
> (Also it was mentioned this would only work for people making a fresh
> clone; anyone with an existing clone would almost certainly know
> something was up.)
No, definitely a MITM attack is feasible that would be fast
forwardable just fine for a pull onto an existing repo.
> Also there is the issue of the book reference, which is hard to
> change. Though, for this, you could just have a dummy server which
> redirects people, something which is essentially:
>
> nc -l -p 9418 -c "echo -n 002AERR please use https://foo.bar/foo.git"
Right, this is exactly what I wound up doing, except much higher
performance using epoll:
https://git.zx2c4.com/git-daemon-dummy/about/
I haven't decided whether or not to deploy it, but the code is there.
> (Of course, someone could still MITM *that*.
Right. But the idea, anyhow, would just be to let the readers of the
book know what's up, rather than leaving them in the dark.
next prev parent reply other threads:[~2016-02-23 5:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 20:43 jea-signup-cgit
2016-02-23 5:05 ` Jason [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-22 19:50 jea-signup-cgit
2016-02-22 19:57 ` webmaster
2016-02-23 5:02 ` Jason
2016-02-22 19:59 ` mailings
2016-02-22 18:16 Jason
2016-02-22 18:22 ` Jason
2016-02-22 19:18 ` mailings
2016-02-22 19:56 ` Jason
2016-02-23 1:19 ` normalperson
2016-02-23 1:28 ` Jason
2016-02-23 5:08 ` Jason
2016-02-23 6:21 ` normalperson
2016-02-24 19:00 ` hacking
2016-02-25 17:21 ` Jason
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=CAHmME9phkpYxS8sSPqwULUtUmtrMeNGhjTdQQJQ_AoonMuNwPA@mail.gmail.com \
--to=cgit@lists.zx2c4.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).