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

Update the dates for ACME v1 EOL
This commit is contained in:
Brendan Abolivier 2020-07-22 16:45:09 +01:00 committed by GitHub
commit a4cf94a3c2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 2 deletions

1
changelog.d/7934.doc Normal file
View file

@ -0,0 +1 @@
Update the dates of ACME v1's end of life in [`ACME.md`](https://github.com/matrix-org/synapse/blob/master/docs/ACME.md).

View file

@ -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