7 ms·
http://en.wikipedia.org/wiki/TCP_Fast_Open http://en.wikipedia.org/wiki/TCP_Fast_Open I guess CentOS will get this in 2020, sigh, still waiting for initrwnd 10
by ck2 14y ago
http://en.wikipedia.org/wiki/TCP_Fast_Open http://en.wikipedia.org/wiki/TCP_Fast_Open
I guess CentOS will get this in 2020, sigh, still waiting for initrwnd 10 support.
- Nux 14y agoIf all you need is the kernel, then you can use the one provided by the elrepo.org project.
- stusmall 14y agoAlso building your own isn't too difficult.
- andreaso 14y agoBuilding a kernel of your own is fairly trivial. The potentially less trivial part is keeping it up-to-date with security fixes, etc. Not impossible by any means, but it does require a bit of a commitment in time, build environment, etc.
- sp332 14y agoWouldn't this conflict with TCP cookies, which were (partially) added to the kernel just a little while ago?
- marshray 14y agoNo, it uses a different TCP options header. In fact, many of the security considerations are the same.
- sp332 14y agoOK, interesting. TCP cookies allocate (practically) no resources to a TCP connection until the three-way handshake is complete, whereas Fast Open can start receiving data before the handshake even finishes. But even if you only do Fast Open on hosts that you have previously completed a normal 3-way handshake with, attackers will just do one full handshake at the beginning of the attack and then switch to SYN flooding.
- caf 14y agoSYN flooding is only really effective if it's spoofed, and you can't spoof a full three-way handshake unless you're in a privileged position on the network.
- pm90 14y agoThe cookies are meant only to avoid resource exhaustion attacks from the processing of the initial data segment.
- marshray 14y agoattackers will just do one full handshake at the beginning of the attack and then switch to SYN flooding Except it's no longer SYN flooding at that point, it's full HTTP request flooding. But in a sense isn't that really the goal of this design? To make it a bit more efficient to get requests to the application layer? In any case, it seems like an application using this feature to have an efficient way of disabling it if it can't handle the current load. Kernels could add efficient heuristics to throttle it automatically too. I'm more concerned that a bug in the entropy of the key generation process could turn these servers into massive reflected DoS amplifiers. E.g., the attacker sends 1 packet with the source address spoofed and the webserver replies with an entire HTTP result to the victim.
- B-Con 14y agoMore detailed explanation here: http://lwn.net/Articles/508865/ http://lwn.net/Articles/508865/
- sliverstorm 14y agoAh, the downsides to stability. The particularly unfortunate part is, as much of the world's commercial hosting runs on RHEL, it's the world that doesn't get this until 2020. Well, except for services that roll custom kernels.
- ck2 14y agoYup - I realize it's the stability in trade. Every so often I am tempted to fiddle with debian, looks like more and more people are thinking that way: http://w3techs.com/blog/entry/debian_is_now_the_most_popular_linux_distribution_on_web_servers http://w3techs.com/blog/entry/debian_is_now_the_most_popular...
- Scramblejams 14y agoI highly recommend making the switch. They've been doing the package management thing the longest, and it shows, both in package selection and how smoothly it all generally runs. And I've never had less trouble upgrading from one version to the next than on Debian.
- thevdude 14y agoDebian was my first linux distro and moving from stable to testing repos the first time was a real pain in the ass. After doing it once or twice, and reading a ton of stuff and learning what was actually going on when I was changing settings, I was much better off.
- sliverstorm 14y agoOn the other hand, one of the nice things about RHEL is you hardly ever have to upgrade major version... RHEL4 has been around since 2005, and is only now finally being phased out. In comparison, I think "sarge" was the stable Debian in 2005. "sarge" is no longer oldstable- nor is etch. oldstable is "lenny", released in 2009. Don't get me wrong, I like Debian, but when you compare "ease of upgrading", don't forget to consider "need to upgrade"!
- mediocregopher 14y agoCentOS 6 actually does support the initrwnd 10 modification. I forget what exactly is involved but we have it working on our servers where I work.
- ck2 14y agoYou are thinking of initcwnd 6.3 still does not support initrwnd which needs a minimum kernel of 2.6.38
- mediocregopher 14y agoAh, you are correct. My mistake.
- jlgreco 14y agoHave you considered using Scientific Linux? It seems to do a much better job of tracking RHEL in a timely manner.
- reidrac 14y agoIt's Red Hat that it's not including stuff in RHEL, not that CentOS is slow tracking features. So you get the same stuff with Scientific Linux (mostly, both SL and CentOS package some extra bits, but overall is RHEL). It's API/ABI stability, and it's meant to be a feature of RHEL.
- allerratio 14y agoRHEL 7 is planned for 2013. If it's released in late 2013 it could get in