Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 26 Mar 2019 11:19:27 +0100
From: Jens Gustedt <>
Subject: Re: Supporting git access via smart HTTPS protocol for


On Mon, 25 Mar 2019 22:59:37 -0400 Rich Felker <> wrote:

> > 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, 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.

One thing you'd have to have in mind is to chose a server for which it
is possible to update the certificate automatically. For some time I
used mini_httpd, which is really minimal footprint, but I had to
update the letsencrypt certificate every three month manually.

Now I switched to nginx and here automatic update of the certificate
works like a charm.


:: INRIA Nancy Grand Est ::: Camus ::::::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536   ::
:: :::::::::::::::::::::: gsm France : +33 651400183   ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: ::

Content of type "application/pgp-signature" skipped

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.