This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Check the TLS certificate matches the fingerprint in the key response when connecting to a server over federation (SYN-457) #1362
Comments
Jira watchers: @NegativeMjark @richvdh |
why is this an important thing to do? People are setting up their synapses with federation behind reverse-proxies and not telling synapse about the cert. If we ever fix it, we're going to break them. In the meantime, confusion reigns. -- @richvdh |
(how do we cope with replacing certs on the reverse-proxy?) -- @richvdh |
apparently we check the tls cert on first connection but not thereafter -- @richvdh |
matrixbot
changed the title
Check the TLS certificate matches the fingerprint in the key response when connecting to a server over federation (SYN-457)
Check the TLS certificate matches the fingerprint in the key response when connecting to a server over federation (https://github.com/matrix-org/synapse/issues/1362)
Nov 7, 2016
matrixbot
changed the title
Check the TLS certificate matches the fingerprint in the key response when connecting to a server over federation (https://github.com/matrix-org/synapse/issues/1362)
Check the TLS certificate matches the fingerprint in the key response when connecting to a server over federation (SYN-457)
Nov 7, 2016
see also matrix-org/matrix-doc#1685 |
MSC1711 proposes that we should instead switch to verifying via Certificate Authorities. |
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
(Imported from https://matrix.org/jira/browse/SYN-457)
(Reported by @NegativeMjark)
The text was updated successfully, but these errors were encountered: