No HTTPS on nginx.org by default

Richard Stanway r1ch+nginx at teamliquid.net
Mon Aug 22 15:40:02 UTC 2016


1. You could provide insecure.nginx.org mirror for such people, make
nginx.org secure by default.

2. Modern server CPUs are already extremely energy efficient, TLS adds
negligible load. See https://istlsfastyet.com/



On Mon, Aug 22, 2016 at 12:31 PM, Valentin V. Bartenev <vbart at nginx.com>
wrote:

> On Sunday 21 August 2016 15:56:09 B.R. wrote:
> > It is surprising, since I remember Ilya Grigorik made a talk about TLS
> > during the first ever nginx conf in 2014:
> > https://www.youtube.com/watch?v=iHxD-G0YjiU
> > https://istlsfastyet.com/
>
> It's just Ilya's opinion.  You are free to agree or not.
>
>
> >
> > Thus, there is no reason for not going full-HTTPS in delivering Web
> pages.
>
> There are at least two reasons to not use HTTPS:
>
>  1. Provide easy access to information for people, who can't use encryption
>     by political, legal, or technical reasons.
>
>  2. Don't waste resources on encryption, and thus save our planet.
>
> Please, don't be a TLS despot and let people to have a choice to use
> encryption
> or not.
>
> I think the situation when I can't download new version of OpenSSL using
> old
> version of OpenSSL is ridiculous, but they have configured openssl.org
> that way.
> How I supposed to use Internet then?
>
>   wbr, Valentin V. Bartenev
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160822/715062aa/attachment.html>


More information about the nginx mailing list