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
Currently there is no protection against serializing too much data and deserializing a message that is too large. Max Message Size is defined in both client and server - and we have no "negotiation" phase which would inform each other of their respective max sizes. A solution needs to be defined for this and implemented.
The text was updated successfully, but these errors were encountered:
Meulengracht
changed the title
[general] add protective measures against buffer overflows
[security] add protective measures against buffer overflows
May 5, 2021
Currently there is no protection against serializing too much data and deserializing a message that is too large. Max Message Size is defined in both client and server - and we have no "negotiation" phase which would inform each other of their respective max sizes. A solution needs to be defined for this and implemented.
The text was updated successfully, but these errors were encountered: