Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport release-23.05] nixos/synapse: allow omitting trusted_key_servers[].verify_keys #233827

Merged
merged 1 commit into from May 25, 2023

Conversation

github-actions[bot]
Copy link
Contributor

Bot-based backport to release-23.05, triggered by a label in #232837.

  • Before merging, ensure that this backport complies with the Criteria for Backporting.
    • Even as a non-commiter, if you find that it does not comply, leave a comment.

Synapse does not require the `verify_keys` attr/object to be set.
It made sense back in the day, when federation traffic used to use self-signed certificates. But this is no longer the case.

The previous `types.nullOr` didn't actually allow omitting `verify_keys` because Synapse's config parser is unable to parse that.

Not a breaking change.

Upstream docs: https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html?highlight=verify_keys#trusted_key_servers

(cherry picked from commit d212ec1)
@emilylange
Copy link
Member

@ofborg test matrix-synapse

@wegank wegank merged commit a28170c into release-23.05 May 25, 2023
20 checks passed
@wegank wegank deleted the backport-232837-to-release-23.05 branch May 25, 2023 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants