Skip to content

Comment on LeaseWeb: Statement on former client MegaUpload

Comments

So the local feds took 60 servers? Out of 690?

I can't tell from the 1HU front plate of a generic server what it's contents are. So maybe those were the only servers they could directly implicate in transmitting copyrighted stuff? But I'm not sure you can even make that distinction (load balancers, proxys, internal networking different from outside view, ..). The charges also included racketeering and other capital crimes, so I'd imagine they could have easily taken all of these servers on that charge alone.

Also, the way searches work here is that the people executing them are usually not involved in the actual investigation. They call it the executive arm for a reason. So they usually get a broad description of what to take (servers), and from whom (Megaupload) and then take everything they can find. Police here commonly confiscates displays when looking for hard disks.

Also, why did LeaseWeb not immediately re-assign after first non-payment? What was the bet here? That MegaUpload would be able to stave off capital charges on absolutely no capital at all (initially), spanning 5+ countries?

From what it looks like, these servers were tainted, and should have been taken in as evidence.

(Whats the connection here with https://www.eff.org/cases/megaupload-data-seizure ?)

The Fed took 60 because those are the ones belong to Dotcom. They probably need to jump through more hoops to take the 630 leased ones. So they didn't bother.

Maybe they just took the servers that were used for/labeled as email or other corporate purposes and left the storage farm that had all the content on? Assuming a segmented network I would think all the corporate servers were on one network (possibly all in the same racks) that was probably obviously labeled and the storage servers were identical arrays on another network.

But then why are there 60 of them? You don't need that much for corporate email.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.