mirrors/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2024-12-19 17:56:19 +03:00
Code Issues Projects Releases Packages Wiki Activity

update timeline

Browse source
This commit is contained in:
Neil Johnson 2019-06-06 11:46:17 +01:00
parent fc45a323ee
commit 4f810e5726
1 changed files with 5 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/MSC1711_certificates_FAQ.md
View file

@ -68,16 +68,14 @@ Admins should upgrade and configure a valid CA cert. Homeservers that require a
.well-known entry (see below), should retain their SRV record and use it .well-known entry (see below), should retain their SRV record and use it
alongside their .well-known record. alongside their .well-known record.
**>= 5th March 2019 - Synapse 1.0.0 is released** **10th June 2019 - Synapse 1.0.0 is released**
1.0.0 will land no sooner than 1 month after 0.99.0, leaving server admins one 1.0.0 is scheduled for release on 10th June. In
month after 5th February to upgrade to 0.99.0 and deploy their certificates. In
accordance with the the [S2S spec](https://matrix.org/docs/spec/server_server/r0.1.0.html) accordance with the the [S2S spec](https://matrix.org/docs/spec/server_server/r0.1.0.html)
1.0.0 will enforce certificate validity. This means that any homeserver without a 1.0.0 will enforce certificate validity. This means that any homeserver without a
valid certificate after this point will no longer be able to federate with valid certificate after this point will no longer be able to federate with
1.0.0 servers. 1.0.0 servers.
## Configuring certificates for compatibility with Synapse 1.0.0 ## Configuring certificates for compatibility with Synapse 1.0.0
### If you do not currently have an SRV record ### If you do not currently have an SRV record