-
Notifications
You must be signed in to change notification settings - Fork 576
deactivate TLSv1 by default #242
Comments
I'm okay to remove TLS1.0 since it seems that TLS1.1 is widely supported. If you have some others suggestions to improve TLS security on the Would you like to submit a PR ? If yes, fell free to submit. Otherwise I can make the change. |
Thanks, but you can make the change. As I don't use the standard HTTPS port SSLLabs doesn't work for me to check for further vulnerabilities. A recommendation (for a TLS1.2 config): Enabling HSTS would also be something to think about it. But that can be annoying with cert problems so I don't recommend it for this project. Edit: |
a little update from my side. I will update my container to 5.0 soon and then test some "casual" security configurations without TLSv1 and then some stronger configurations. Then I test it some weeks (colleagues will be my Guinea pigs) and then you will hear from me again with a proper tested working config. |
security > interoperability drop everything but v1.2, let the unfortunate souls misconfigure their servers on their own |
TLSv1.3 support has just been added to nginx on Alpine. |
We will probably deprecate the |
Hi,
today I've seen that TLS 1.0 and 1.1 is on by default under web/mattermost-ssl
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
I recommend to reject at least TLSv1. Would be nice if we could edit it in the docker-compose.yml.
The text was updated successfully, but these errors were encountered: