From 894ac30a4e44e53a8116e6597f74a0d58ae495c6 Mon Sep 17 00:00:00 2001
From: MatMaul
This setting should only be used in very specific cases, such as federation over Tor hidden services and similar. For private networks of homeservers, you likely want to use a private CA instead.
-Only effective if federation_verify_certicates
is true
.
Only effective if federation_verify_certificates
is true
.
Example configuration:
federation_certificate_verification_whitelist:
- lon.example.com
@@ -1462,12 +1462,12 @@ Defaults to per_second: 0.1
, burst_count: 5
.
-
address
ratelimits login requests based on the client's IP
-address. Defaults to per_second: 0.17
, burst_count: 3
.
+address. Defaults to per_second: 0.003
, burst_count: 5
.
-
account
ratelimits login requests based on the account the
-client is attempting to log into. Defaults to per_second: 0.17
,
-burst_count: 3
.
+client is attempting to log into. Defaults to per_second: 0.03
,
+burst_count: 5
.
-
failed_attempts
ratelimits login requests based on the account the
@@ -2023,8 +2023,8 @@ however, the interface is documented
An alternative to registration_shared_secret
:
allows the shared secret to be specified in an external file.
The file should be a plain text file, containing only the shared secret.
-If this file does not exist, Synapse will create a new signing
-key on startup and store it in this file.
+If this file does not exist, Synapse will create a new shared
+secret on startup and store it in this file.
Example configuration:
registration_shared_secret_path: /path/to/secrets/file
--
cgit 1.5.1