during some testing i found that the server logs each time a client sends a bad reducer call with a log like this
this is one client calling it every 100ms with bad parameters.
- one log would be enough per client
- it should disconnect the client as the client is clearly broken or someone is trying to make a custom client and got the parameters wrong.
right now this is a DOS attack point as it fills the logs and as reducers aren't rate limited, it can spam the logs with a call every microsecond or faster. (1000+ bad requests per second but theoretically 10k+ bad requests per second).
during some testing i found that the server logs each time a client sends a bad reducer call with a log like this
this is one client calling it every 100ms with bad parameters.
right now this is a DOS attack point as it fills the logs and as reducers aren't rate limited, it can spam the logs with a call every microsecond or faster. (1000+ bad requests per second but theoretically 10k+ bad requests per second).