diff options
| author | Neil Johnson <neil@matrix.org> | 2019-06-10 17:40:00 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-06-10 17:40:00 +0100 |
| commit | 1bfab2f8ad03193852d132e5a8eb29f9134d9f45 (patch) | |
| tree | dc4c619544ef14e8f68970cb911a555d0e6d8518 | |
| parent | reword for clarity (diff) | |
| download | synapse-1bfab2f8ad03193852d132e5a8eb29f9134d9f45.tar.xz | |
typos
| -rw-r--r-- | docs/MSC1711_certificates_FAQ.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/MSC1711_certificates_FAQ.md b/docs/MSC1711_certificates_FAQ.md index d0d4a88a48..7f9a23ff31 100644 --- a/docs/MSC1711_certificates_FAQ.md +++ b/docs/MSC1711_certificates_FAQ.md @@ -2,10 +2,10 @@ ## Historical Note This document was originally written to guide server admins through the upgrade -path towards Synapse 1.0.0. Specifically, +path towards Synapse 1.0. Specifically, [MSC1711](https://github.com/matrix-org/matrix-doc/blob/master/proposals/1711-x509-for-federation.md) required that all servers present valid TLS certificates on their federation -API. Admins were encouraged to achieve compliance from version 0.99.0 (release +API. Admins were encouraged to achieve compliance from version 0.99.0 (released in February 2019) ahead of version 1.0 (released June 2019) enforcing the certificate checks. |