summary refs log tree commit diff
path: root/setup.py (unfollow)
Commit message (Collapse)AuthorFilesLines
2020-09-29Add argument specifying whether 3pid check is happening during registrationAndrew Morgan2-4/+8
2020-09-29Add some logging around checking 3PIDs are allowedAndrew Morgan1-0/+13
2020-09-28Don't check whether a 3pid is allowed to register during password reset github/anoa/info-mainline-no-check-password-reset-backport anoa/info-mainline-no-check-password-reset-backportAndrew Morgan1-7/+0
This check was preventing people from resetting their passwords unless they already had a pending invite to that email address, which makes no sense.
2020-09-24s/URLs/variables in changelog v1.20.1 github/release-v1.20.1 release-v1.20.1Andrew Morgan1-1/+1
2020-09-24s/accidentally/incorrectly in changelogAndrew Morgan1-1/+1
2020-09-24Update changelog wordingAndrew Morgan1-1/+1
2020-09-241.20.1Andrew Morgan5-3/+17
2020-09-24Mark the shadow_banned column as boolean in synapse_port_db. (#8386)Patrick Cloke3-0/+2
2020-09-24Hotfix: disable autoescape by default when rendering Jinja2 templates (#8394)Andrew Morgan3-3/+12
#8037 changed the default `autoescape` option when rendering Jinja2 templates from `False` to `True`. This caused some bugs, noticeably around redirect URLs being escaped in SAML2 auth confirmation templates, causing those URLs to break for users. This change returns the previous behaviour as it stood. We may want to look at each template individually and see whether autoescaping is a good idea at some point, but for now lets just fix the breakage.
2020-09-22Fix wording of deprecation notice in changelog v1.20.0 github/release-v1.20.0 release-v1.20.0Andrew Morgan1-5/+4
2020-09-22Deprecation warning for synapse admin api being accessible under /_matrixAndrew Morgan1-1/+13
2020-09-221.20.0Andrew Morgan3-3/+13
2020-09-18Add a note about including the changes from 1.19.3. v1.20.0rc5Patrick Cloke1-0/+2
2020-09-18Tweak wording in the changelog.Patrick Cloke1-2/+2
2020-09-181.20.0rc5Patrick Cloke6-5/+23
2020-09-181.19.3 v1.19.3 github/release-v1.19.3 release-v1.19.3Andrew Morgan4-2/+16
2020-09-18Use _check_sigs_and_hash_and_fetch to validate backfill requests (#8350)Andrew Morgan2-5/+4
This is a bit of a hack, as `_check_sigs_and_hash_and_fetch` is intended for attempting to pull an event from the database/(re)pull it from the server that originally sent the event if checking the signature of the event fails. During backfill we *know* that we won't have the event in our database, however it is still useful to be able to query the original sending server as the server we're backfilling from may be acting maliciously. The main benefit and reason for this change however is that `_check_sigs_and_hash_and_fetch` will drop an event during backfill if it cannot be successfully validated, whereas the current code will simply fail the backfill request - resulting in the client's /messages request silently being dropped. This is a quick patch to fix backfilling rooms that contain malformed events. A better implementation in planned in future.
2020-09-18Intelligently select extremities used in backfill. (#8349)Erik Johnston4-20/+67
Instead of just using the most recent extremities let's pick the ones that will give us results that the pagination request cares about, i.e. pick extremities only if they have a smaller depth than the pagination token. This is useful when we fail to backfill an extremity, as we no longer get stuck requesting that same extremity repeatedly.
2020-09-18Add flags to /versions about whether new rooms are encrypted by default. (#8343)Patrick Cloke2-0/+20
2020-09-18Fix ratelimiting for federation `/send` requests. (#8342)Erik Johnston4-17/+54