matrix/thirdparty/synapse.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Files	Lines
2020-09-22	Deprecation warning for synapse admin api being accessible under /_matrix	Andrew Morgan	1	-1/+13

2020-09-22	1.20.0	Andrew Morgan	3	-3/+13

2020-09-18	Add a note about including the changes from 1.19.3. v1.20.0rc5	Patrick Cloke	1	-0/+2

2020-09-18	Tweak wording in the changelog.	Patrick Cloke	1	-2/+2

2020-09-18	1.20.0rc5	Patrick Cloke	6	-5/+23

2020-09-18	1.19.3 v1.19.3 github/release-v1.19.3 release-v1.19.3	Andrew Morgan	4	-2/+16

2020-09-18	Use _check_sigs_and_hash_and_fetch to validate backfill requests (#8350)	Andrew Morgan	2	-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-18	Intelligently select extremities used in backfill. (#8349)	Erik Johnston	4	-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.
2