From mboxrd@z Thu Jan  1 00:00:00 1970
From: jea-signup-cgit at anakata.org (Joe Anakata)
Date: Mon, 22 Feb 2016 11:50:42 -0800
Subject: Killing plaintext git:// in favor of https:// cloning
In-Reply-To: Your message dated "Mon, 22 Feb 2016 20:18:06 +0100."
Message-ID: <20160222195042.99D6C82323@gnosis.slac.com>


On 22/02/16 19:16, Jason A. Donenfeld wrote:

>> Now that git.zx2c4.com runs over HTTPS, I'm considering getting rid of
>> the plaintext git:// endpoint for cloning.

Ferry Huberts Proclaimed Thus: 

>Yes, why?
>What's the point?
>
>The repos are public, so cloning them over https bring nothing, except 
>extra overhead and server load.

While pretty unlikely, in theory someone could MITM a git:// clone and
send the user a hax0red branch of cgit with integrated botnet which
the user then compiles and installs on their server.

Not sure if the extra server load is worth it to defend against this
case or not.  (Also, presumably the server is using the cgit smart http
endpoint so https clone is not much additional DATA, just the ssl
handshake; but definitely additional cpu for crypto operations.)

Thanks
-Joe