summary refs log tree commit diff
path: root/synapse/crypto
diff options
context:
space:
mode:
authorAndrew Morgan <1342360+anoadragon453@users.noreply.github.com>2020-09-18 14:51:11 +0100
committerGitHub <noreply@github.com>2020-09-18 14:51:11 +0100
commit27c1abc7b876ef3e73c8b418a89b987f86147829 (patch)
tree3a22f90364995856582f79c319057e3677b36c16 /synapse/crypto
parent1.19.2 (diff)
downloadsynapse-27c1abc7b876ef3e73c8b418a89b987f86147829.tar.xz
Use _check_sigs_and_hash_and_fetch to validate backfill requests (#8350)
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.
Diffstat (limited to 'synapse/crypto')
0 files changed, 0 insertions, 0 deletions