On 22 July 2015 at 05:36, Enrico Tröger <enrico.troe...@uvena.de> wrote: > On 21/07/15 14:54, Jiří Techet wrote: >> On Tue, Jul 21, 2015 at 6:58 AM, Lex Trotman <ele...@gmail.com> wrote: >> >>> If its gonna be hosted on Geany projects server it needs to be HTTPS >>> and that means getting a "real" certificate accepted by browsers. > > Could you please elaborate why "it needs" to be reachable via HTTPS? > Just for my curiosity.
For the same reason that github went all https, and thats even with all of git's sha checking. I'll bet almost nobody checks the sig of the tarballs. Cheers Lex > > I will setup the plugins website now and it will be reachable via HTTPS > with the same SSL certificate as the main Geany website, the certificate > has a wildcard for *.geany.org. > > >> HTTPS isn't used for Geany tarballs or binaries from >> >> http://www.geany.org/Download/Releases >> >> so it doesn't have to be used for the plugins either (may be a nice-to-have >> but not required IMO). > > No doubt on "nice to have". > This is the same as for the Geany website itself. We need to solve the > certificate issue. Though it is a seperate issue. > > > Regards, > Enrico > > -- > Get my GPG key from http://www.uvena.de/pub.asc > > > _______________________________________________ > Devel mailing list > Devel@lists.geany.org > https://lists.geany.org/cgi-bin/mailman/listinfo/devel > _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel
