This is a good article. Click here for more information.

AACS encryption key controversy

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

Internet users began circulating versions of this image, calling it the Free Speech Flag, in blog posts on dozens of websites and as user avatars on forums such as Digg. The first fifteen bytes of the 09 F9 key are contained in the RGB encoding of the five colors, with each color providing three bytes of the key. The byte "C0" is appended in the lower right corner.[1][2][3][4][5][6]

A controversy surrounding the AACS cryptographic key arose in April 2007 when the Motion Picture Association of America and the Advanced Access Content System Licensing Administrator, LLC (AACS LA) began issuing cease and desist letters[7] to websites publishing a 128-bit (16-byte) number, represented in hexadecimal as 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0[8][9] (commonly referred to as 09 F9),[10][11] a cryptographic key for HD DVDs and Blu-ray Discs. The letters demanded the immediate removal of the key and any links to it, citing the anti-circumvention provisions of the United States Digital Millennium Copyright Act (DMCA).

In response to widespread Internet postings of the key, the AACS LA issued various press statements, praising those websites that complied with their requests as acting in a "responsible manner", warning that "legal and technical tools" were adapting to the situation.

The controversy was further escalated in early May 2007, when aggregate news site Digg received a DMCA cease and desist notice and then removed numerous articles on the matter and banned users reposting the information.[12] This sparked what some describe as a digital revolt[13] or "cyber-riot",[14] in which users posted and spread the key on Digg, and throughout the Internet en masse, thereby leading to a Streisand effect. The AACS LA described this situation as an "interesting new twist".[15]

Background

Hexadecimal is a base-16 numeral system used in the fields of computer programming and mathematics. The key is an ordinary number most widely known by its hexadecimal representation; in decimal notation, it is 13,256,278,887,989,457,651,018,865,901,401,704,640.[16]

Because the encryption key may be used as part of circumvention technology forbidden by the DMCA, its possession and distribution has been viewed as illegal by the AACS, as well as by some legal professionals.[7][17] Since it is a 128-bit numerical value, it was dubbed an illegal number.[18][19][20] Opponents to the expansion of the scope of copyright criticize the idea of making a particular number illegal.[21]

Commercial HD DVDs and Blu-ray Discs integrate copy protection technology specified by the AACS LA. There are several interlocking encryption mechanisms, such that cracking one part of the system does not necessarily crack other parts. Therefore, the "09 F9" key is only one of many parts that are needed to play a disc on an unlicensed player.

The AACS system can be used to revoke a key of a specific playback device, after it is known to have been compromised, as it has for WinDVD.[22] The compromised players can still be used to view old discs, but not newer releases without encryption keys for the compromised players. If other players are then cracked, further revocation would lead to legitimate users of compromised players being forced to upgrade or replace their player software or firmware in order to view new discs. Each playback device comes with a binary tree of secret device and processing keys. The processing key in this tree, a requirement to play the AACS encrypted discs, is selected based on the device key and the information on the disc to be played. As such, a processing key such as the "09 F9" key is not revoked, but newly produced discs cause the playback devices to select a different valid processing key to decrypt the discs.[23]

Timeline of AACS cracking

2006

On December 26, 2006, a person using the alias muslix64 published a utility named BackupHDDVD and its source code on the DVD decryption forum at the website Doom9.[24] BackupHDDVD can be used to decrypt AACS protected content once one knows the encryption key.[25] muslix64 claimed to have found title and volume keys in main memory while playing HD DVDs using a software player, and that finding them is not difficult.[26]

2007

On January 1, 2007, muslix64 published a new version of the program, with volume key support.[27] On January 12, 2007, other forum members detailed how to find other title and volume keys, stating they had also found the keys of several movies in RAM while running WinDVD.

On or about January 13, a title key was posted on pastebin.com in the form of a riddle, which was solved by entering terms into the Google search engine. By converting these results to hexadecimal, a correct key could be formed.[28] Later that day, the first cracked HD DVD, Serenity, was uploaded on a private torrent tracker.[29] The AACS LA confirmed on January 26 that the title keys on certain HD DVDs had been published without authorization.[30]

Doom9.org forum user arnezami found and published the "09 F9" AACS processing key on February 11:[31]

<templatestyles src="Template:Blockquote/styles.css" />

Nothing was hacked, cracked or even reverse engineered btw: I only had to watch the "show" in my own memory. No debugger was used, no binaries changed.

This key is not specific to any playback device or DVD title. Doom9.org forum user jx6bpm claimed on March 4 to have revealed CyberLink's PowerDVD's key, and that it was the key in use by AnyDVD.[32]

The AACS LA announced on April 16 that it had revoked the decryption keys associated with certain software high-definition DVD players, which will not be able to decrypt AACS encrypted disks mastered after April 23, without an update of the software.[33][34]

On May 17, one week before any discs with the updated processing key had reached retail, claims were reported of the new keys having been retrieved from a preview disc of The Matrix Trilogy.[35] On May 23, the key 45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2 was posted on Edward Felten's Freedom to Tinker Blog[36] and confirmed a week later by arnezami on Doom9 as the new processing key (MKB v3).[37]

2008

In August, two new processing keys were posted:[38]

  • F1 90 A1 E8 17 8D 80 64 34 94 39 4F 80 31 D9 C8, for MKB v4, and
  • 7A 5F 8A 09 F8 33 F7 22 1B D4 1F A6 4C 9C 79 33, which appeared to work with MKB v6, MKB v7 and MKB v8 discs.

2009

In March, two additional processing keys were posted:[39]

  • C8 72 94 CE 84 F9 CC EB 59 84 B5 47 EE C1 8D 66, for MKB v9
  • 45 2F 6E 40 3C DF 10 71 4E 41 DF AA 25 7D 31 3F, for MKB v10

While individual discs have been decrypted containing media key block version 17,[40] processing keys for versions past 10 have not yet been released to the public.[41]

Many more later keys were discovered, but most were not released publicly, probably because that would make them easier to revoke.[42]

DMCA notices and Digg

Screenshot of the Digg front page during the user revolt; all stories are related to the HD DVD key.

As early as April 17, 2007, AACS LA had issued DMCA violation notices, sent by Charles S. Sims of Proskauer Rose.[43][44] Following this, dozens of notices were sent to various websites hosted in the United States.[45]

On May 1, 2007, in response to a DMCA demand letter, technology news site Digg began closing accounts and removing posts containing or alluding to the key. The Digg community reacted by creating a flood of posts containing the key, many using creative ways of semi-directly or indirectly inserting the number, such as in song or images (either representing the digits pictorially or directly representing bytes from the key as colors) or on merchandise.[46] At one point, Digg's "entire homepage was covered with links to the HD-DVD code or anti-Digg references."[47] Eventually the Digg administrators reversed their position, with founder Kevin Rose stating:

<templatestyles src="Template:Blockquote/styles.css" />

But now, after seeing hundreds of stories and reading thousands of comments, you've made it clear. You'd rather see Digg go down fighting than bow down to a bigger company. We hear you, and effective immediately we won't delete stories or comments containing the code and will deal with whatever the consequences might be.[48][49][50]

Legal opinions

Lawyers and other representatives of the entertainment industry, including Michael Ayers, an attorney for Toshiba Corporation, expressed surprise at Digg's decision, but suggested that a suit aimed at Digg might merely spread the information more widely.

<templatestyles src="Template:Blockquote/styles.css" />

If you try to stick up for what you have a legal right to do, and you're somewhat worse off because of it, that's an interesting concept.

— Michael Ayers, Toshiba Corp.[51]

The American Bar Association's eReport published a discussion of the controversy,[52] in which Eric Goldman at Santa Clara University's High Tech Law Institute noted that the illegality of putting the code up is questionable (that Section 230 of the Communications Decency Act may protect the provider when the material itself is not copyrighted), although continuing to allow posting of the key may be "risky", and entertainment lawyer Carole Handler noted that even if the material is illegal, laws such as the DMCA may prove ineffective in a practical sense.

Impact

In a response to the events occurring on Digg and the call to "Spread this number", the key was rapidly posted to thousands of pages, blogs and wikis across the Internet.[53][54] The reaction was an example of the Streisand effect.[55]

Intellectual property lawyer Douglas J. Sorocco noted, "People are getting creative. It shows the futility of trying to stop this. Once the information is out there, cease-and-desist letters are going to infuriate this community more."[52] Outside the Internet and the mass media, the key has appeared in or on T-shirts, poetry, songs and music videos, illustrations and other graphic artworks,[56] tattoos and body art,[57] and comic strips.[58]

On Tuesday afternoon, May 1, 2007, a Google search for the key returned 9,410 results,[59] while the same search the next morning returned nearly 300,000 results.[9] On Friday, the BBC reported that a search on Google shows almost 700,000 pages have published the key,[15] despite the fact that on April 17, the AACS LA sent a DMCA notice to Google, demanding that Google stop returning any results for searches for the key.[60][61]

Widespread news coverage[62] included speculation on the development of user-driven websites,[63] the legal liability of running a user-driven website,[64] the perception of acceptance of DRM,[65] the failure as a business model of "secrecy based businesses ... in every aspect" in the Internet era,[66] and the harm an industry can cause itself with harshly-perceived legal action.[67]

In an opposing move, Carter Wood of the National Association of Manufacturers said they had removed the "Digg It"-link from their weblog.[68]

<templatestyles src="Template:Blockquote/styles.css" />

Until the Digg community shows as much fervor in attacking intellectual piracy as attacking the companies that are legitimately defending their property, well, we do not want to be promoting the site by using the "Digg It" feature.

Media coverage initially avoided quoting the key itself. However, several US-based news sources have run stories containing the key, quoting its use on Digg,[69][70][71][72][73][74] though none are known to have received DMCA notices as a result. Later reports have discussed this, quoting the key.[75] Current TV broadcast the key during a Google Current story on the Digg incident on May 3, 2007, displaying it in full on screen for several seconds and placing the story on the station website.[76]

Wikipedia, on May 1, 2007, locked out the page named for the number "to prevent the former secret from being posted again. The page on HD DVD was locked, too, to keep out The Number."[77] This action was later reversed.

AACS LA reaction

On May 7, 2007, the AACS LA announced on its website that it had "requested the removal solely of illegal circumvention tools, including encryption keys, from a number of web sites", and that it had "not requested the removal or deletion of any ... discussion or commentary". The statement continued, "AACS LA is encouraged by the cooperation it has received thus far from the numerous web sites that have chosen to address their legal obligations in a responsible manner."[78] BBC News had earlier quoted an AACS executive saying that bloggers "crossed the line", that AACS was looking at "legal and technical tools" to confront those who published the key, and that the events involving Digg were an "interesting new twist".[15]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 15.2 Lua error in package.lua at line 80: module 'strict' not found.
  16. Read as: "thirteen undecillion, two hundred and fifty-six decillion, two hundred and seventy-eight nonillion, eight hundred and eighty-seven octillion, nine hundred and eighty-nine septillion, four hundred and fifty-seven sextillion, six hundred and fifty-one quintillion, eighteen quadrillion, eight hundred and sixty-five trillion, nine-hundred and one billion, four hundred and one million, seven hundred and four thousand, six hundred and forty"
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Blogger News Network / ‘Illegal Number’ Triggers Flood of MPAA Cease-and Desist Letters
  19. ButtUgly: Main_blogentry_010507_1
  20. Protected Blog Login « WordPress.com
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. 52.0 52.1 Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. |url=http://www.foxnews.com/wires/2007May02/0,4670,TechBitDiggRebellion,00.html |date=20070509033240 Forbes at the Wayback Machine (archived May 4, 2007), CNet, BBC, Financial Times, Associated Press Archive copy at the Wayback Machine
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. It’s No Secret: Code Stirs Up a Web Storm[dead link]
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.

External links