Skip to content
Snippets Groups Projects
Unverified Commit a4cf94a3 authored by Brendan Abolivier's avatar Brendan Abolivier Committed by GitHub
Browse files

Merge pull request #7934 from matrix-org/babolivier/acme_eol

Update the dates for ACME v1 EOL
parents 923c9950 55f2617f
No related branches found
No related tags found
No related merge requests found
Update the dates of ACME v1's end of life in [`ACME.md`](https://github.com/matrix-org/synapse/blob/master/docs/ACME.md).
...@@ -12,13 +12,14 @@ introduced support for automatically provisioning certificates through ...@@ -12,13 +12,14 @@ introduced support for automatically provisioning certificates through
In [March 2019](https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430), In [March 2019](https://community.letsencrypt.org/t/end-of-life-plan-for-acmev1/88430),
Let's Encrypt announced that they were deprecating version 1 of the ACME Let's Encrypt announced that they were deprecating version 1 of the ACME
protocol, with the plan to disable the use of it for new accounts in protocol, with the plan to disable the use of it for new accounts in
November 2019, and for existing accounts in June 2020. November 2019, for new domains in June 2020, and for existing accounts and
domains in June 2021.
Synapse doesn't currently support version 2 of the ACME protocol, which Synapse doesn't currently support version 2 of the ACME protocol, which
means that: means that:
* for existing installs, Synapse's built-in ACME support will continue * for existing installs, Synapse's built-in ACME support will continue
to work until June 2020. to work until June 2021.
* for new installs, this feature will not work at all. * for new installs, this feature will not work at all.
Either way, it is recommended to move from Synapse's ACME support Either way, it is recommended to move from Synapse's ACME support
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment