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
As per #148 we applied some rate limiting mechanisms for preventing amplification attacks. But to truly protect against this we need to implement a simple proof of work for making signalling requests.
The rate limiter is still quite basic atm, I had an upgraded design here #148 (comment).
Rate limiting wise, it's not guaranteed to prevent DOS. Only proof of work can do so. But it's a quick way of rate limiting based on certain identifiers. So it can be expanded further. Could combine proof of work along with some bucketing mechanism as a general "resource governor". It sort of reminds me of the resource-counter library that we have.
CMCDragonkai
changed the title
Proof of work rate limiting for NAT signalling
Proof of work rate limiting for NAT signalling and relaying
Oct 24, 2023
Specification
As per #148 we applied some rate limiting mechanisms for preventing amplification attacks. But to truly protect against this we need to implement a simple proof of work for making signalling requests.
Additional context
Tasks
The text was updated successfully, but these errors were encountered: