# 启用 TLS 1.3
**URL:** https://meta.discourse.org/t/enabling-tls-1-3/119789
**Category:** Feature
**Created:** [2019年六月8日 07:08 UTC](https://meta.discourse.org/t/enabling-tls-1-3/119789 "2019-06-08T07:08:57Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Alexander\_Wright](https://meta.discourse.org/u/Alexander_Wright)
#### Post date: [2019年六月8日 07:08 UTC](https://meta.discourse.org/t/enabling-tls-1-3/119789/1 "2019-06-08T07:08:57Z")
Is it possible to enable TLS 1.3 on Discourse? How is the local Nginx configured?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2019年六月8日 09:13 UTC](https://meta.discourse.org/t/enabling-tls-1-3/119789/2 "2019-06-08T09:13:16Z")
We disabled TLS 1.0 and 1.1 in mid 2018 per [this topic](https://meta.discourse.org/t/as-of-october-31-2018-microsoft-office-365-will-no-longer-support-tls-1-0-and-1-1/80479/13).
Do we have TLS 1.3 support at least enabled somewhere @mpalmer?
> **[Can I use... Support tables for HTML5, CSS3, etc](https://caniuse.com/#feat=tls1-3)**
>
> "Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.
---
### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [2019年六月11日 05:56 UTC](https://meta.discourse.org/t/enabling-tls-1-3/119789/3 "2019-06-11T05:56:19Z")
No, I don’t think we’ve turned on TLS 1.3 anywhere yet.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2019年六月11日 07:46 UTC](https://meta.discourse.org/t/enabling-tls-1-3/119789/4 "2019-06-11T07:46:30Z")
We run NGINX 1.5 at the moment in the containers:
Per:
>
We only enable `TLSv1.2`
I am mixed on enabling TLSv1.3 until [RFC 8446: The Transport Layer Security (TLS) Protocol Version 1.3 | RFC Editor](https://www.rfc-editor.org/info/rfc8446) is ratified though.
For the time being simply adding another template after the ssl template with:
```plaintext
- 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)
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [2019年九月2日 18:34 UTC](https://meta.discourse.org/t/enabling-tls-1-3/119789/9 "2019-09-02T18:34:10Z")
我们刚刚发布了支持 TLS 1.3 的新基础镜像 🎉。
> [@Discourse new Base Image](https://meta.discourse.org/t/discourse-new-base-image/127427?u=falco):
>
> We just released a new base image with support for TLS 1.3 tada. Users will need to rebuild from the command line to get this new feature. We also packed a few dependencies update, moved from Ubuntu 16.04 to Debian Buster and updated our SSL cyphers list to match [https://ssl-config.mozilla.org/](https://ssl-config.mozilla.org/) intermediate config and updated to Ruby 2.6.4. Due to all that we will make the command line rebuild mandatory later this week.
---
### Author:  [@MikeNolan](https://meta.discourse.org/u/MikeNolan)
#### Post date: [2023年三月25日 21:39 UTC](https://meta.discourse.org/t/enabling-tls-1-3/119789/10 "2023-03-25T21:39:07Z")
当我在容器内查看 nginx 配置文件时，它具有以下设置：
# SSL 设置
```
ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; # 弃用 SSLv3，参考：POODLE
```
由于 BEAST 攻击，TLSv1 和 TLSv1.1 的引用是否应该被删除？
两个不同的网站检查器告诉我 TLSv1 和 TLSv1.1 未启用，不确定它们是从哪里禁用的。
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [2023年三月27日 02:55 UTC](https://meta.discourse.org/t/enabling-tls-1-3/119789/11 "2023-03-27T02:55:39Z")
这在这里定义
>