Date: Tue, 26 Mar 2019 11:04:30 -0400 From: Rich Felker <dalias@...c.org> To: musl@...ts.openwall.com Subject: Re: Supporting git access via smart HTTPS protocol for musl-libc On Tue, Mar 26, 2019 at 03:32:46PM +0530, vlse wrote: > On Mon, Mar 25, 2019 at 10:59:37PM -0400, Rich Felker wrote: > > On Tue, Mar 26, 2019 at 07:24:35AM +0530, vlse wrote: > > > Hi, > > > > > > On Mon, Mar 25, 2019 at 09:37:06PM -0400, Rich Felker wrote: > > > > On Mon, Mar 25, 2019 at 08:17:26PM -0500, A. Wilcox wrote: > > > > > On 03/25/19 20:09, vlse wrote: > > > > > > Hello, > > > > > > > > > > > > But for internet git access, either ssh or https smart protocol use > > > > > > is necessary to prevent man in the middle attack. > > > > > > > > > > > > > The request is reasonable. HTTPS is *not* "trivial to MITM", and > > > > essentially impossible to do so without detection and a trail of > > > > you can also verify authenticity of a git repo via "git fsck" and a > > > > known good source of the commit hash (e.g. cgit over https). > > > > > > > > > > Yes. cgit over https. We need a secure start first. > > > > > > > > > Please consider giving secure git access. Also smart http/s protocol > > > > > > is way better than dumb protocol. It avoids downloading too much data > > > > > > again and also shows progress and stats. > > > > > > > > > > > > > Of course the git transport won't be taken away. I'd like to add https > > > > support, but I'm not sure how to do it without a nasty bloated httpd > > > > that would increase server resource requirements by 1-2 orders of > > > > magnitude. If anyone knows a way to hook up thttpd to it, I'll give it > > > > a try. > > > > > > Nginx is bloat free I think. But perhaps not in comparison to thttpd. > > > I will look how to support cgit http/s with thttpd using a hook. > > > > > > At skarnet.org, the author is using busybox httpd with cgi support and > > > cgit cgi hooks to give http/s git access. > > > > OK, that sounds promising. If it can be done with cgi, it should be > > easy to setup, assuming the git client is forgiving of thttpd's > > slightly non-conforming cgi behavior regarding headers. > > > > Rich > > Hi, > > On further enquiry I found that the latest cgit only supports dumb http protocol > for cloning or fetch. But it has option to disable the http/s cloning support, > so that another program can do it. Sorry, I was on the impression that skarnet was > supporting git http/s smart protocol by using cgit itself. > > So we have to setup the git-http-backend provided with git-scm to work with web > server cgi setup. Again the examples given at upstream site is with apache. As long as it's cgi and not sensitive to thttpd cgi conformance issues, it should work. > So I am thinking of trying setting up thttpd with git-scm for support of http/s smart > protocol locally in my linux machine. > > So I want to know the > Source of thttpd your are running on git.musl-libc.org > Version of thttpd > > Latest upstream version: https://acme.com/software/thttpd/thttpd-2.29.tar.gz It's the version in Alpine Linux which also has some significant bug fixes on top of that. > Also I find you are providing https version of git.musl-libc.org site. > thttpd does not supports https. Are you using stunnel for it? I'm presently using haproxy's TLS-layer (vs HTTPS-layer) proxying, because stunnel suggers from a 2.5-decades-old wrong handling of TCP connection closing that makes it unusable, and because haproxy is what I knew at the time. I think openssl s_server could handle it too, but might not support SNI (?). What I'd really prefer is a non-broken stunnel workalike using BearSSL as the backend, since BearSSL is the only non-awful TLS implementation. If anyone wants to work on something like that I'd be happy to test and eventually dogfood it on musl site. Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.