On Tue, Jul 19, 2016 at 11:19:48AM +0100, Paul Jakma wrote: > On Wed, 13 Jul 2016, David Lamparter wrote: > > > I've just installed the most recent version of patchwork; the upgrade > > was a bit bumpy - please report any malfunctions. It looks quite a > > bit different since upstream moved to bootstrap for styling, but > > functionally there isn't much different. > > > There is now also a https URL available at: > > https://patchwork.diac24.net > > in addition to the usual: > > http://patchwork.quagga.net > > > > Cheers, > > Thanks David, > > I think you should be able to get an HTTPS cert for the latter hostname > from LetsEncrypt. I'll mail you the scripts off-list that I use for > bugzilla, etc., that seem to work there.
Thanks; the problem there is a different one though - my hosting setup has a separate reverse proxy doing all TLS handling; i.e. the patchwork setup can't access its own certificates. I'm using the ACME DNS method to get my LetsEncrypt certificates for my own domains (which the TLS box handles perfectly on its own, and I like the clear security zoning with that); on the other hand the HTTP method becomes very cumbersome to use since I'd need to push either the auth-tokens or certificates around between zones. For now I'm very tempted to not sink additional time into it and leave it as https://patchwork.diac24.net -- is there a real demand/need to have https://patchwork.quagga.net too? (http of course still works on both names) Cheers, -David _______________________________________________ Quagga-dev mailing list [email protected] https://lists.quagga.net/mailman/listinfo/quagga-dev
