Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-03 10:14:10 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Remove .well-known section

Browse source 
This really belongs in MSC1708.
This commit is contained in:
Richard van der Hoff 2019-01-07 21:39:02 +00:00
parent 367f61f14a
commit 74b2db7937
1 changed files with 0 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
proposals/1711-x509-for-federation.md
View file

@ -105,22 +105,6 @@ the recommendations of
[RFC6125](https://tools.ietf.org/html/rfc6125#section-6.2.1) and the
conventions established by the XMPP protocol (per [RFC6120](https://tools.ietf.org/html/rfc6120#section-13.7.2.1).
### Interaction with `.well-known` files
[MSC1708](https://github.com/matrix-org/matrix-doc/blob/rav/proposal/well-known-for-federation/proposals/1708-well-known-for-federation.md)
proposes an alternative to SRV records, in the form of `.well-known` files. In
this instance, a file at `https://matrix.org/.well-known/matrix/server` might
direct requests to `server.example.com`.
In this case, `server.example.com` would be required to present a valid
certificate for `server.example.com`.
Because the request for the `.well-known` file takes place over a validated TLS
connection, this is not subject to the same DNS-based attacks as the SRV
record, and this mechanism allows the owners of a domain to delegate
responsibility for running their Matrix homeserver without having to hand over
TLS keys for the whole domain.
### Extensions
HTTP-Based Public Key Pinning (HPKP) and