Is it possible to enable TLS 1.3 on Discourse? How is the local Nginx configured?
We disabled TLS 1.0 and 1.1 in mid 2018 per this topic.
Do we have TLS 1.3 support at least enabled somewhere @mpalmer?
No, I don’t think we’ve turned on TLS 1.3 anywhere yet.
We run NGINX 1.5 at the moment in the containers:
We only enable
I am mixed on enabling TLSv1.3 until Information on RFC 8446 » RFC Editor is ratified though.
For the time being simply adding another template after the ssl template with:
- replace: hook: ssl filename: "/etc/nginx/conf.d/discourse.conf" from: ssl_protocols TLSv1.2; to: | ssl_protocols TLSv1.2 TLSv1.3;
Would do the trick, the question though is if this is a trick you want to do given the protocol is still not ratified (even though it is being implemented)
I gues you allready knew that but only chaning the ssl_protocols wont help because the underlying nginx and openssl version has to support it which is not the case ATM on the docker base image.
We just release a new base image with support for TLS 1.3 .
When I look at the nginx config file inside the container, it has these settings:
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # Dropping SSLv3, ref: POODLE
Should the references to TLSv1 and TLSv1.1 be dropped because of the BEAST attack?
Two different site checkers tell me TLSv1 and TLSv1.1 are not enabled, not sure where they’re disabled from.
That’s defined here