News for hackers. Stuff that matters.
Re:An introduction to JavaScript-based DDoS by userbinator on Thursday April 30, 2015 @11:39AM (#9465738)
You don't even need JS to perform "DDoS" - simply link to an image or some other resource on the target site from another site with high traffic, and you accomplish essentially the same effect. Forums that allow linking to images/etc. in inline posts and/or signatures are another way to "gather a crowd", and I've accidentally DDoS'd in this way too... not unlike the "slashdot effect". In fact it could be argued that HTTPS makes DDoS even more effective, due to the additional overhead it introduces on each connection.

I think per-IP rate limiting is one of the best ways of preventing DDoS - stop answering clients that issue too many requests in a short time and they will probably choke on their own open-connections limit very soon as the connections start timing out, since the packets are coming from the browser initiating TCP connections and not a dedicated packet-spewing program.

Re:An introduction to JavaScript-based DDoS by hn_ on Thursday April 30, 2015 @01:01PM (#9466248)
I remember "hot-linking" was a big problem in the 1990s web.

Also one time a myspace template linked to pictures on some guys website and became really popular. He decided to goatse the myspace profiles who were hot-linking his photos.

Re:An introduction to JavaScript-based DDoS by kpcyrd on Thursday April 30, 2015 @01:28PM (#9466394)
Re:An introduction to JavaScript-based DDoS by timboslice on Thursday April 30, 2015 @03:18PM (#9467062)
Risky click of the day after seeing Goatse mentioned above. It was actually a pretty good read, thanks for sharing!
Re:An introduction to JavaScript-based DDoS by heatish on Thursday April 30, 2015 @01:24PM (#9466365)
How effective would per-IP rate limiting be for these new types of JS attacks though? As I understand it, it's just the sheer number of requests that they can get sent to the server with these types of attacks rather than say a botnet spamming requests over and over from the couple hundred PC's they have under their control or a HTTP POST attack where they trickle in the body of the request to hang up the server.