diff options
| author | Dirk Klimpel <5740567+dklimpel@users.noreply.github.com> | 2021-10-05 13:35:19 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-10-05 11:35:19 +0000 |
| commit | 7036a7a60af54dec2e1ad5e4c31a450817a68147 (patch) | |
| tree | 317bf3bae33625a8144489fa7f4e457740191403 | |
| parent | Log stack traces when a missing opentracing span is detected (#10983) (diff) | |
| download | synapse-7036a7a60af54dec2e1ad5e4c31a450817a68147.tar.xz | |
Update links to MSCs in documentation (#10991)
Based on matrix-doc switching from master -> main and MSCs being merged.
| -rw-r--r-- | changelog.d/10991.doc | 1 | ||||
| -rw-r--r-- | docs/MSC1711_certificates_FAQ.md | 4 | ||||
| -rw-r--r-- | docs/usage/administration/admin_api/registration_tokens.md | 3 |
3 files changed, 5 insertions, 3 deletions
diff --git a/changelog.d/10991.doc b/changelog.d/10991.doc new file mode 100644 index 0000000000..2f9bb24ca7 --- /dev/null +++ b/changelog.d/10991.doc @@ -0,0 +1 @@ +Update links to MSCs in documentation. Contributed by @dklimpel. \ No newline at end of file diff --git a/docs/MSC1711_certificates_FAQ.md b/docs/MSC1711_certificates_FAQ.md index 7d71c190ab..086899a9d8 100644 --- a/docs/MSC1711_certificates_FAQ.md +++ b/docs/MSC1711_certificates_FAQ.md @@ -3,7 +3,7 @@ ## Historical Note This document was originally written to guide server admins through the upgrade 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 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 @@ -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 certificates for federation alongside the rest of the Web. More details can be 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 for the security model. However, the existence of Let's Encrypt as a trivial diff --git a/docs/usage/administration/admin_api/registration_tokens.md b/docs/usage/administration/admin_api/registration_tokens.md index 828c0277d6..c48d060dcc 100644 --- a/docs/usage/administration/admin_api/registration_tokens.md +++ b/docs/usage/administration/admin_api/registration_tokens.md @@ -1,7 +1,8 @@ # Registration Tokens 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 option, and authenticate by providing an `access_token` for a server admin: see [Admin API](../../usage/administration/admin_api). |