diff options
author | Richard van der Hoff <1389908+richvdh@users.noreply.github.com> | 2022-02-04 11:27:00 +0000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-02-04 11:27:00 +0000 |
commit | b3d155a749a7881806d985fe85d8ed20b16dbaf0 (patch) | |
tree | 16899752a6993c61a2e2f5730734674fd351882e /docs/upgrade.md | |
parent | Merge remote-tracking branch 'origin/master' into develop (diff) | |
download | synapse-b3d155a749a7881806d985fe85d8ed20b16dbaf0.tar.xz |
Delete MSC1711_certificates_FAQ.md (#11907)
This document isn't really relevant any more, and its existence is more confusing than helpful.
Diffstat (limited to '')
-rw-r--r-- | docs/upgrade.md | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/docs/upgrade.md b/docs/upgrade.md index 7d582af0a7..75febb4adf 100644 --- a/docs/upgrade.md +++ b/docs/upgrade.md @@ -1142,8 +1142,7 @@ more details on upgrading your database. Synapse v1.0 is the first release to enforce validation of TLS certificates for the federation API. It is therefore essential that your -certificates are correctly configured. See the -[FAQ](MSC1711_certificates_FAQ.md) for more information. +certificates are correctly configured. Note, v1.0 installations will also no longer be able to federate with servers that have not correctly configured their certificates. @@ -1208,9 +1207,6 @@ you will need to replace any self-signed certificates with those verified by a root CA. Information on how to do so can be found at the ACME docs. -For more information on configuring TLS certificates see the -[FAQ](MSC1711_certificates_FAQ.md). - # Upgrading to v0.34.0 1. This release is the first to fully support Python 3. Synapse will |