So I suppose this bug wouldn't affect an Erlang-based web server like yaws, because the Erlang VM is actually supposed to handle 100000 threads.
Anyway, is this bug HTTP-protocol specific? I'd guess it can affect any services which are expected to keep a session open for a long time, if the client can use a lot less memory for each connection than the server...
Posted Jun 25, 2009 9:52 UTC (Thu) by Darkmere (subscriber, #53695)
[Link]
This "bug" is the same as the SMTP tarpit and others, but instead of working on the server side, it works on the client side, against the server.
So, it works on the same basis that so many other attacks do, find a limited resource on the server, find a way to make the server hit that limit, lean back and reap profits.