From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: Killing plaintext git:// in favor of https:// cloning
Date: Tue, 23 Feb 2016 06:08:24 +0100 [thread overview]
Message-ID: <CAHmME9oJ5wnd2y5smLe0MF16Ao9TB8VNTX__sHOvPK5qYPCMRA@mail.gmail.com> (raw)
In-Reply-To: <20160223011957.GA788@dcvr.yhbt.net>
On Tue, Feb 23, 2016 at 2:19 AM, Eric Wong <normalperson at yhbt.net> wrote:
> I suggest keeping git:// running as automated mirrors may not be
> monitored very closely or easily updated.
That's a good point. I'd forgotten about automated mirrors. I'll keep
logs of the git:// pulls for a month or so and see if there are any
regular pullers and also if I can track down the source IP. Perhaps
it's a manageable pool of people to switch over.
> git already has plenty of integrity checking built-in and
> getting the proper hashes for the heads/tags over a
> trusted-enough medium is enough (or reading the fine code).
No, git's built-in integrity protection really is not sufficient if
the transport is compromised.
> And as others have said, HTTPS isn't impenetrable
I'd like some specific details on this repeated claim.
> the CA system is still a major problem.
True. But there doesn't appear to be a widely deployed alternative.
> Also, TLS libraries can introduce new bugs and vulnerabilities
> like Heartbleed.
This is true, but I already require a public TLS deployment, so it's
there regardless.
next prev parent reply other threads:[~2016-02-23 5:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2016-02-23 6:21 ` normalperson
[not found] ` <CANyOob14C3cZuwkQBpEv=Tr==KY=oULyUg7NX3B6vb8mfRkgDg@mail.gmail.com>
2016-02-23 14:03 ` [pass] " Jason
[not found] ` <CANyOob1KEfFd5-e5e9ETauvmakEiK7pU5083-7t8CzTW5-QrKQ@mail.gmail.com>
2016-02-23 14:34 ` Jason
2016-02-24 19:00 ` hacking
2016-02-25 17:21 ` Jason
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 20:43 jea-signup-cgit
2016-02-23 5:05 ` 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=CAHmME9oJ5wnd2y5smLe0MF16Ao9TB8VNTX__sHOvPK5qYPCMRA@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).