We reported back in February on the latest HD-DVD and Blu-ray encryption cracking efforts by the Doom9 forum members. At that time a AACS encryption media key was discovered, a key that can be used by unapproved software to identify itself as a validly licensed player of HD-def discs. The argument is often presented that without such keys, users of linux and unsupported OS platforms have no options for playing the new AACS encrypted media. So there is a valid fair use argument, similar to the DeCSS issues of yesteryear. The AACS keys can of course also be used to decrypt discs and copy/redistribute them illegally. Personally, I believe fair use entitles you to a personal backup copy, but that’s another argument entirely…

Anyway, about two weeks ago, AACS lawyers issued cease and desist letters to a number of prominent websites, blogs, and search engines, invoking the DMCA and calling for prompt removal of any references to the AACS 16-digit hex code, and furthermore any references to sites where the code is available. The notices infer that links to such sites would be subject to the takedown notice, which some find a debatable issue. The four main URLs they note in the notices are listed, and ironically one of the site addresses consists partly of the 32-bit code in question. Nice.

Here is an example of one such notice: “It is our understanding that you are providing to the public the above-identified tools and services at the above referenced URL, and are thereby providing and offering to the public a technology, product, service, device, component, or part thereof that is primarily designed, produced, or marketed for the purpose of circumventing the technological protection measures afforded by AACS (hereafter, the “circumvention offering”). Doing so constitutes a violation of the anti-circumvention provisions of the Digital Millennium Copyright Act.”

One site that preemptively began removing links to the code was the “pop links” aggregator Digg. It didn’t take long for Digg users (“Diggers” *sigh*) to take notice that stories and links were being removed. After several accounts were suspended for posting the links, the users began a revolt which continued for a good day at least. They began posting stories and links referencing the hex code at a dizzying pace, voting the stories to the top of the heap. For a good part of Tuesday, the Digg front page consisted completely of stories referencing the code. Some were pretty creative in their use of the code, here’s a good example. Finally, the founders of Digg responded, bowing to users wishes. For now the Digg userbase is happy, but legal issues remain to be seen.

The flurry of activity wasn’t limited to Digg, oh no:
*Wikipedia blocked new articles on the code (ironically preserving the code forever…look at that link).

*As of last night, I noted a good 270K+ hits on a google search for the code itself.

*The Electronic Frontier Foundation explains the legalities of linking to the code (basically, because of the over-arching nature of the DMCA laws, the AACS organization actually has a leg to stand on).

*David Chartier suggests that the “revolting” Diggers consider putting their money where their mouth is and actually DOING SOMETHING to help change the DRM landscape. “…Users went nuts, calling out digg for ‘bowing down to the man’ and bitching that their right to free speech was being violated…..Most people who I see posting this code in a unified “F-Uâ€? to digg or the man also typically rant about how bad DRM is for the industry and how, in their opinion, it isn’t actually effective in protecting content…..I want everyone who is opposed to DRM to start offering some options on how to fix the problem and then start doing something about it. Organize a protest, call your senator, get on the news, kick up some dirt – but start using all this technology at our disposal to help things move forward.” Sounds like a reasoned argument to me!

And finally, it’s been noted that AACS-encoded discs created after April 23 can’t be cracked by the number. Anyone wish to speculate on how long it’ll be until the next code is cracked? Because it most assuredly with be discovered at one point or another.

To make this a bit more fun, we’ll give the closest crack date guess a shiny new FreshDV tee. Go on, take a stab at it…
UPDATE: Looks like the new crack already happened, a few weeks ago. And is supposedly unfixable.

UPDATE: More reading on this topic can be found here, including a very well done article by the Times; “…its relentless spread has already become a lesson in mob power on the Internet and the futility of censorship in the digital world.”