Hacker News new | past | comments | ask | show | jobs | submit login
How LulzSec kept itself safe during the summer of 'lulz' (newscientist.com)
66 points by jgrahamc on Feb 28, 2012 | hide | past | favorite | 33 comments



Very interesting headline followed by a total content-less fluffy press release masquerading as a news story.

I am, as they say, disappoint.


I found this pretty interesting:

> "but we also saw very specific attacks targeted at vulnerabilities in the routers we used on our network. That's pretty clever; you would have to spend quite a bit of time investigating the topology in order to figure out what routers we were using."


If only that had gone on for more than a sentence, especially with asking permission to talk about the situation.


I agree. I was hoping for some investigative reporting, but the entire story is an advertisement.


Nice ad Cloudfare... Wait, was it a legit article ?

NewScientist took a hit in my heart in terms of credibility with this article.


Yes, it was a vendor interview piece with a linkbait-and-switch title. (Cloudfare didn't keep Lulzsec "safe", they kept their website up.)

But NewScientist's primary audience is not web hosting specialists. So for their audience I expect it was mildly educational.


If I remember correctly some guy posted lulzsec member identities online after simply following them in irc..


Indeed, but none of them led to the arrests.

It's very likely that they were false IDs created for diversion.


How LulzSec kept -- their website -- safe during the summer of 'lulz'


Yes, they didn't do a particularly good job of keeping themselves safe, did they?


My bullshit detector went off somewhere around here: "CloudFlare provides performance and security for any website online.We handle more traffic through our network now than Amazon, Wikipedia, Twitter, Zynga and Aol combined."

Considering Wiki, Twitter and Amazon are all top 10 global sites, I'm having a hard time imagining someone doing more traffic than all of them put together, even disregarding the rounding errors of Zynga/AOL. Anyone have more concrete statistics to confirm/deny this?


Here's our internal data on this. Based on page view data (values below are page views) and using the statistics from Google DoubleClick Ad Planner (http://www.google.com/adplanner/static/top1000/) we have the following for the last 30 days:

    Wikipedia.org    6,000,000,000
    Twitter.com      5,900,000,000
    Amazon.com       4,900,000,000
    Aol.com          5,400,000,000
    Zynga.com          460,000,000
    Total           22,660,000,000
Then looking at our own internal network for the last 30 days we see:

    CloudFlare      27,066,719,054								
So we did about 4.4B more page views than the combined sites above which would actually leave us room to add LinkedIn and Flickr to the list.


Much of Twitter and Zynga's "traffic" won't show up as pageviews - they'll be API calls that Ad Planner wouldn't pick up.

Regardless, that is a pretty remarkable amount of data. What makes it worth carrying at zero cost?


Are you confident that you're comparing apples to apples there, and not e.g. pageviews to http requests?


Yes. We have detailed stats on page views, hits, bandwidth, cache hits, etc. etc. Looking at the most recent data which I get daily I see in the trailing 30 days: 27B page views and 162B hits.


LuzSec did not 'disappear'. They became Anti-Sec, and they are still around.


While I don't have any statistics, I do not doubt their claim. CloudFlare is a CDN, and as such will handle an enormous amount of traffic. As an example of this, Akamai, a large CDN, handles approximately 20% of the total traffic on the internet. In fact, many sites, such as Wikipedia, Twitter, even Amazon and Google, actually host static content through Akamai. All this content adds up to significant amounts of traffic.

EDIT: Link -- http://www.akamai.com/html/technology/dataviz3.html


My understanding is that CloudFlare runs a CDN delivering content for thousands and thousands of sites. This means it basically has to handle all the traffic for all of its customers. I'm sure that adds up really quickly.


It doesn't seem that surprising. Just digging around in the passive DNS database at work, I see CloudFlare has their name servers in the NS records of several 10's of thousands of domains. I'm fairly sure that given the scope of the sources of this data, that list is nowhere near complete.


My understanding of cloud flare is that they null route you if any major attack comes in- Seems a little bit unfair they didnt do this for lulzsec just to get the press. If you are some boring website that gets the same attack lulzsec does, they will just disconnect/nullroute you.

Correct me if any of this inaccurate, but last I checked it was not.


Hi,

We only force a site direct if the attack is too large & starts to impact other customers as well. If the attack doesn't impact other customers, then we won't force the site direct (we generally only force a few sites direct per week & these are monster attacks).


How was it that the Lulzsec attacks were not as large? What qualifies a sufficient size attack?


Also:

Clarifying that forcing direct does not mean a null route. Forcing direct = going direct to the site's server (we still resolve the DNS).


Yes. This happened to our site as well. Cloudflare buckled and sent a "sorry, can't handle it" email.


This is very true as I saw it first hand around the very same time.


Nice press hit.


does anyone have experience with cloudflare? good service?


I've used it on a few small websites.

I think it's a great service if you don't want to spend money on a cdn.


I've used it a few times and it works well, it certainly didn't hurt. It's interesting to look at the stats they give and see how much bad traffic is being blocked. They definitely curbed the amount of comment spam on a test Wordpress blog I was using for awhile.

I wish I had more exact, measurable, information to provide but I used it only out of curiosity.


I tried them out for a bit, mostly because of their always-on claim but it didn't work for my sites for some reason so I switched to Amazon.

Their interface is nice, but I don't like the fact that you have to switch your DNS over to them and then re-enter data like MX records. With amazon I just point the parts of my domains I want to use to them and the rest remains with my primary DNS hosting.


if you email them you can get onto the private CNAME beta!


Is router/server fingerprinting really that "clever." Looks like 5 minutes with nmap and nessus.


How is someone trying to take down a website they don't like a "white hat" hacker?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: