Cryptome in Hot Water Again

garg0yle writes to tell us that Cryptome appears to have stepped in it again with a recent leaked document concerning Microsoft's "Global Criminal Compliance Handbook." "Microsoft has demanded that Cryptome take down the guide — on the grounds that it constitutes a 'copyrighted [work] published by Microsoft.' Yesterday, at 5pm, Cryptome editor John Young received a notice from his site’s host, Network Solutions, bearing a stiff ultimatum: citing the Digital Millennium Copyright Act (DMCA), Network Solutions told him that unless he takes the 'copyrighted material' down, they will 'disable [his] website' on Thursday, February 25, 2010. So far, Young refuses to budge." In a gesture of goodwill, Wikileaks has offered to host Cryptome via their twitter feed.

Comments

Already gone?

[tomalpha]

Looks like DNS has already gone...

Searching for cryptome.org. A record at G.ROOT-SERVERS.NET. [192.112.36.4] ...took 31 ms
Searching for cryptome.org. A record at D0.ORG.AFILIAS-NST.org. [199.19.57.1] ...took 9 ms

Nameserver D0.ORG.AFILIAS-NST.org. reports: No such host cryptome.org

Re:Already gone?

[Anonymous Coward]

The document is already available via wikileaks.

Re:Already gone?

[dgatwood]

It astonishes me that anyone still uses Network Solutions. Their extensive list of blocks for transferring domain services (read: anytime you'd actually want to, you're prevented) is mind-boggling.

Agreed. It astonishes me even more, however, that an organization like this would do so, and doubly so that anyone in their right minds doing anything more than a personal vanity site would use the same provider for both hosting and domain name registration. That's just asking for a hard-to-fix DMCA shutdown of the site, loss of the site due to the ISP going bankrupt, loss of the domain due to any number of billing disagreements with the ISP that are unrelated to the domain name registration, etc.

AFAIK, the DMCA does *not* provide for locking the domain registration of a claimed-infringing site, only providing for the takedown of the content. However, if your ISP decides it is easier to kill your DNS and lock the domain to prevent transferring it than to muck with your server account, you're stuck. Why? Because you are using the same provider for hosting and (massively overpriced) domain name registration. Don't DO that.

If I were one of these folks, I'd register my domain in a neutral country. For example, you can register .com domains with Gandi.net in France or with NameForName in Russia, or... well, here's a list of ICANN-accredited registrars, most of which support the .com registry. Find one in a country that has as few ACTA-like agreements with the U.S. as possible. Even with the exchange rates as bad as they are, those two I mentioned still charge less than half what NetSol charges for a domain name, with the added security of making it much harder to attack the domain itself with a mere DMCA takedown notice.