From ff6d08fe71b8a49b1cf2ff70adda0bfef61469d0 Mon Sep 17 00:00:00 2001 From: DMRobertson Date: Fri, 28 Oct 2022 12:55:51 +0000 Subject: deploy: 44f0d573cf57772b7f53e918d0c3580cba4fde32 --- develop/usage/configuration/config_documentation.html | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'develop/usage') diff --git a/develop/usage/configuration/config_documentation.html b/develop/usage/configuration/config_documentation.html index 7c9ed54cb7..47729d8a29 100644 --- a/develop/usage/configuration/config_documentation.html +++ b/develop/usage/configuration/config_documentation.html @@ -2300,6 +2300,11 @@ is still supported for backwards-compatibility, but it is deprecated.

trusted_key_servers defaults to matrix.org, but using it will generate a warning on start-up. To suppress this warning, set suppress_key_server_warning to true.

+

If the use of a trusted key server has to be deactivated, e.g. in a private +federation or for privacy reasons, this can be realised by setting +an empty array (trusted_key_servers: []). Then Synapse will request the keys +directly from the server that owns the keys. If Synapse does not get keys directly +from the server, the events of this server will be rejected.

Options for each entry in the list include: