@@ -633,6 +633,12 @@ uploads_path: "{{SYNAPSE_ROOT}}uploads"
633633#
634634enable_registration : true
635635
636+ # Enable registration without email or captcha verification. Note: this option is *not* recommended,
637+ # as registration without verification is a known vector for spam and abuse. Defaults to false. Has no effect
638+ # unless `enable_registration` is also enabled.
639+ #
640+ enable_registration_without_verification : true
641+
636642# The user must provide all of the below types of 3PID when registering.
637643#
638644# registrations_require_3pid:
@@ -792,13 +798,50 @@ signing_key_path: "{{SYNAPSE_ROOT}}localhost.signing.key"
792798
793799# The trusted servers to download signing keys from.
794800#
795- # perspectives:
796- # servers:
797- # "matrix.org":
798- # verify_keys:
799- # "ed25519:auto":
800- # key: "Noi6WqcDj0QmPxCNQqgezwTlBKrfqehY1u2FyWP9uYw"
801+ # When we need to fetch a signing key, each server is tried in parallel.
802+ #
803+ # Normally, the connection to the key server is validated via TLS certificates.
804+ # Additional security can be provided by configuring a `verify key`, which
805+ # will make synapse check that the response is signed by that key.
806+ #
807+ # This setting supercedes an older setting named `perspectives`. The old format
808+ # is still supported for backwards-compatibility, but it is deprecated.
809+ #
810+ # 'trusted_key_servers' defaults to matrix.org, but using it will generate a
811+ # warning on start-up. To suppress this warning, set
812+ # 'suppress_key_server_warning' to true.
813+ #
814+ # Options for each entry in the list include:
815+ #
816+ # server_name: the name of the server. required.
817+ #
818+ # verify_keys: an optional map from key id to base64-encoded public key.
819+ # If specified, we will check that the response is signed by at least
820+ # one of the given keys.
821+ #
822+ # accept_keys_insecurely: a boolean. Normally, if `verify_keys` is unset,
823+ # and federation_verify_certificates is not `true`, synapse will refuse
824+ # to start, because this would allow anyone who can spoof DNS responses
825+ # to masquerade as the trusted key server. If you know what you are doing
826+ # and are sure that your network environment provides a secure connection
827+ # to the key server, you can set this to `true` to override this
828+ # behaviour.
829+ #
830+ # An example configuration might look like:
831+ #
832+ # trusted_key_servers:
833+ # - server_name: "my_trusted_server.example.com"
834+ # verify_keys:
835+ # "ed25519:auto": "abcdefghijklmnopqrstuvwxyzabcdefghijklmopqr"
836+ # - server_name: "my_other_trusted_server.example.com"
837+ #
838+ trusted_key_servers :
839+ - server_name : " matrix.org"
801840
841+ # Uncomment the following to disable the warning that is emitted when the
842+ # trusted_key_servers include 'matrix.org'. See above.
843+ #
844+ suppress_key_server_warning : true
802845
803846# Enable SAML2 for registration and login. Uses pysaml2.
804847#
0 commit comments