New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(relay): check message data doesn't exceed a configurable limit #195
Conversation
Should I also add a flag to the configuration to set wether the size limit is enforced, like we do for signature verification and account balance? @authcall |
yes that sounds good. I think something like |
…igurable limit (#195) * feat(relay): check message data doesn't exceed a configurable limit * feat(relay): add config flag to enforce data size limit * fix: revert typos * fix: revert more not needed changes * Update README.md Co-authored-by: authcall <authcall@proton.me>
…atticexyz#195) * feat(relay): check message data doesn't exceed a configurable limit * feat(relay): add config flag to enforce data size limit * fix: revert typos * fix: revert more not needed changes * Update README.md Co-authored-by: authcall <authcall@proton.me>
Right now, the data field of a relayed message can have an arbitrary size so it's possible for an attacker to send a giant message. This PR adds a field to the relay server configuration specifying a size limit for message data.