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?
2 „Gefällt mir“
No, I don’t think we’ve turned on TLS 1.3 anywhere yet.
3 „Gefällt mir“
We run NGINX 1.5 at the moment in the containers:
Per:
https://github.com/discourse/discourse_docker/blob/master/templates/web.ssl.template.yml#L21
We only enable TLSv1.2
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)
5 „Gefällt mir“
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 
.
8 „Gefällt mir“
Wenn ich die Nginx-Konfigurationsdatei im Container betrachte, hat sie diese Einstellungen:
SSL-Einstellungen
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # SSLv3 wird verworfen, Ref: POODLE
Sollten die Verweise auf TLSv1 und TLSv1.1 wegen des BEAST-Angriffs verworfen werden?
Zwei verschiedene Website-Checker sagen mir, dass TLSv1 und TLSv1.1 nicht aktiviert sind. Ich bin mir nicht sicher, wo sie deaktiviert sind.
Das ist hier definiert