OpenCloud
/
MatrixSynapse
mirror of https://github.com/matrix-org/synapse
1
0
Fork 0
Code Issues Releases Wiki Activity

Update links to MSCs in documentation (#10991) 

Based on matrix-doc switching from master -> main and
MSCs being merged.
pull/10993/head
Dirk Klimpel 2021-10-05 13:35:19 +02:00 committed by GitHub
parent 660c8c1415
commit 7036a7a60a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
changelog.d/10991.doc Normal file
View File

@ -0,0 +1 @@
Update links to MSCs in documentation. Contributed by @dklimpel.

4
docs/MSC1711_certificates_FAQ.md
View File

@ -3,7 +3,7 @@
## Historical Note ## Historical Note
This document was originally written to guide server admins through the upgrade This document was originally written to guide server admins through the upgrade
path towards Synapse 1.0. Specifically, path towards Synapse 1.0. Specifically,
[MSC1711](https://github.com/matrix-org/matrix-doc/blob/master/proposals/1711-x509-for-federation.md) [MSC1711](https://github.com/matrix-org/matrix-doc/blob/main/proposals/1711-x509-for-federation.md)
required that all servers present valid TLS certificates on their federation required that all servers present valid TLS certificates on their federation
API. Admins were encouraged to achieve compliance from version 0.99.0 (released 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 in February 2019) ahead of version 1.0 (released June 2019) enforcing the
@ -282,7 +282,7 @@ coffin of the Perspectives project (which was already pretty dead). So, the
Spec Core Team decided that a better approach would be to mandate valid TLS Spec Core Team decided that a better approach would be to mandate valid TLS
certificates for federation alongside the rest of the Web. More details can be certificates for federation alongside the rest of the Web. More details can be
found in found in
[MSC1711](https://github.com/matrix-org/matrix-doc/blob/master/proposals/1711-x509-for-federation.md#background-the-failure-of-the-perspectives-approach). [MSC1711](https://github.com/matrix-org/matrix-doc/blob/main/proposals/1711-x509-for-federation.md#background-the-failure-of-the-perspectives-approach).
This results in a breaking change, which is disruptive, but absolutely critical This results in a breaking change, which is disruptive, but absolutely critical
for the security model. However, the existence of Let's Encrypt as a trivial for the security model. However, the existence of Let's Encrypt as a trivial

3
docs/usage/administration/admin_api/registration_tokens.md
View File

@ -1,7 +1,8 @@
# Registration Tokens # Registration Tokens
This API allows you to manage tokens which can be used to authenticate This API allows you to manage tokens which can be used to authenticate
registration requests, as proposed in [MSC3231](https://github.com/govynnus/matrix-doc/blob/token-registration/proposals/3231-token-authenticated-registration.md). registration requests, as proposed in
[MSC3231](https://github.com/matrix-org/matrix-doc/blob/main/proposals/3231-token-authenticated-registration.md).
To use it, you will need to enable the `registration_requires_token` config To use it, you will need to enable the `registration_requires_token` config
option, and authenticate by providing an `access_token` for a server admin: option, and authenticate by providing an `access_token` for a server admin:
see [Admin API](../../usage/administration/admin_api). see [Admin API](../../usage/administration/admin_api).