You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Submitted by @matthew:matrix.org
If people are hammering us too rapidly on /sync without a timeout or with too small a timeout, presumably we should insert an implicit timeout to slow them down. c.f. the current DoS from 93.92.200.183
The text was updated successfully, but these errors were encountered:
matrixbot
changed the title
We shouldn't let people DoS us via /sync (SYN-660)
We shouldn't let people DoS us via /sync (https://github.com/matrix-org/synapse/issues/1239)
Nov 7, 2016
matrixbot
changed the title
We shouldn't let people DoS us via /sync (https://github.com/matrix-org/synapse/issues/1239)
We shouldn't let people DoS us via /sync (SYN-660)
Nov 7, 2016
This can be abused very easily with request that one does not care answer for, just fire away... sent PoC on security email. In order of seconds to make our quite beefy HS to OOM...
dkasak
added
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
A-Sync
defects related to /sync
labels
Apr 26, 2022
Submitted by @matthew:matrix.org
If people are hammering us too rapidly on /sync without a timeout or with too small a timeout, presumably we should insert an implicit timeout to slow them down. c.f. the current DoS from 93.92.200.183
(Imported from https://matrix.org/jira/browse/SYN-660)
The text was updated successfully, but these errors were encountered: