3 ms·
This bug really just falls in with "You didn't encrypt and authenticate your data, so anything could have happened". Sure, this time it's a software design bug
by londons_explore 7y ago
This bug really just falls in with "You didn't encrypt and authenticate your data, so anything could have happened".
Sure, this time it's a software design bug in the endpoints, but next time it might be a cosmic ray, or an evil middleman, or a buggy proxy. If data isn't encrypted and authenticated, then you shouldn't care what form it arrives in.
- platz 7y agoYou realize this is talking about TCP, right? You're referring to things that happen in a different OSI layer
- ldite 7y agoThis bug falls in with "reasons connection attempts to your server may be mysteriously failing" - this is a bug in connection setup, when you'll be setting up your secure connection.
- fh973 7y agoNo, it's not that easy. It may also mean your transmission live-locks because your receiving state machine is waiting for more data that never arrives. Yes, it needs a failure detection mechanism, because next time it might be a cosmic ray. But encryption and authentication alone doesn't help necessarily.
- cesarb 7y agoNothing in this post says that the data wasn't authenticated; in fact, the symptom they saw (the client is kicked off because the server doesn't understand the message) is exactly what would happen if the data was authenticated.
- Majromax 7y agoThe data's authenticated, but the authentication is accidentally broken. SYN(seq_num) and SYN(seq_num+3) can both generate the same cookie using a different (but still valid) maximum segment size. To lump this into an existing category of bugs, syn cookies are a kind of HMAC, only the implementation is custom and nonstandard. It isn't a surprise that a bespoke HMAC leaks, but to the credit of kernel developers syn cookies the initial 1996 specification pre-dates the common understanding. (But to its demerit, it looks like the DJB spec (http://cr.yp.to/syncookies.html http://cr.yp.to/syncookies.html) would have not had this issue, since the MSS was encoded in the top bits of the cookie and not the bottom bits.)
- im3w1l 7y agoA malicious client could make sure that you get valid but different data depending on whether noticed something was up. Maybe fool a logging/firewalling middlebox.