diff options
| author | IndeedNotJames <git@indeednotjames.com> | 2023-05-19 15:38:07 +0200 |
|---|---|---|
| committer | IndeedNotJames <git@indeednotjames.com> | 2023-05-19 15:46:53 +0200 |
| commit | d212ec13b8907f631606f0130f6cd73e10b95285 (patch) | |
| tree | f74731dffc3ef7e2947f5610373ad09bb08feeb7 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | 48a0fb7aab511df92a17cf239c37f2bd2ec9ae3a (diff) | |
nixos/synapse: allow omitting `trusted_key_servers[].verify_keys`
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
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions