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
Crow does not check the mask bit, instead it applies the mask regardless (since the mask is always 0 if the mask bit is not set), but this would still involve memory allocation, asio reading, and a loop containing XOR and MOD operations.
a better implementation would be to check the mask bit and ignore any operation if the bit isn't set.
The text was updated successfully, but these errors were encountered:
Update: I was incorrect, crow just shuts the connection if the message is not masked. I'm almost sure this isn't how it should work, especially if we're using SSL
The-EDev
changed the title
Crow does not check for MASK bit in websockets
Crow does not accept 0 MASK bit in websockets
Nov 4, 2020
Crow does not check the mask bit, instead it applies the mask regardless (since the mask is always 0 if the mask bit is not set), but this would still involve memory allocation, asio reading, and a loop containing XOR and MOD operations.
a better implementation would be to check the mask bit and ignore any operation if the bit isn't set.
The text was updated successfully, but these errors were encountered: