Jump to content

BD+

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by GreenC bot (talk | contribs) at 02:01, 10 June 2022 (Rescued 3 archive links. Wayback Medic 2.5). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

BD+ is a component of the Blu-ray Disc digital rights management system. It was developed by Cryptography Research Inc. and is based on their Self-Protecting Digital Content concept.[1] Its intent was to prevent unauthorized copies of Blu-ray discs and the playback of Blu-ray media using unauthorized devices.

While BD+ has not stemmed the flow of "cracked" high-definition content, it has made it necessary for those who wish to copy Blu-ray movies to reinvest resources to break each new version of security code.[2]

BD+ played a pivotal role in the format war of Blu-ray and HD DVD. Several studios cited Blu-ray Disc's adoption of the BD+ anti-copying system as the reason they supported Blu-ray Disc over HD DVD. The copy protection scheme was to take "10 years" to crack, according to Richard Doherty, an analyst with Envisioneering Group.[3]

On 19 November 2007, Macrovision announced that it planned to acquire the SPDC technology (including patents and software code) from CRI for US$45 million in cash plus stock warrants.[4]

On 7 July 2011, Irdeto acquired BD+ content protection technology for Blu-ray discs from Rovi Corporation.[5][6]

Capabilities

BD+ is effectively a virtual machine embedded in authorized players. It allows content providers to include executable programs on Blu-ray Discs. Such programs can:[7]

  • examine the host environment, to see if the player has been tampered with. Every licensed playback device manufacturer must provide the BD+ licensing authority with memory footprints that identify their devices.
  • verify that the player's keys have not been changed.
  • execute native code, possibly to patch an otherwise insecure system.
  • transform the audio and video output. Parts of the content will not be viewable without letting the BD+-program repair it.

If a playback device manufacturer finds that its devices have been hacked, it can potentially release BD+-code that detects and circumvents the vulnerability. These programs can then be included in all new disc releases.[8]

The specifications of the BD+ virtual machine are only officially available to licensed device manufacturers. A list of licensed adopters is available from the BD+ website.[9] Both SlySoft (now RedFox) and members of the Doom9 forum have reverse engineered the virtual machine specification, however.

According to the reverse-engineered specification, the virtual machine consists of a 32-bit big endian DLX like processor with 4MB of RAM. It has 32 32-bit registers available for use. A TRAP instruction is used to allow the virtual machine host to perform more complex actions as system calls.[10]

To prevent simple, static disassembly of the BD+ code, an instruction filter is available that can perform an XOR operation on an opcode before executing it. By varying the instruction filter at runtime, the compiler can force an adversary to trace through the code at runtime before they can fully disassemble it.[11]

Virtual machine

This program which can be found inside the BDSVM directory of a BD+ protected disc is called content code.[10] The content code is executed on a virtual big endian DLX-like processor interfacing 4MB of memory. The processor supports 59 different instructions and a register set consisting of 32 general purpose registers and three special purpose registers for the instruction filter, the clock cycle counter and the program counter. The BD+ Virtual Machine applies memory protection by masking memory access addresses to prevent them from falling outside of the designated memory areas. The execution of content code starts at address 0x1000 relative to the beginning of the payload of the first block of the file 00001.svm (located inside the BDSVM directory).

Traps

While the BD+ virtual machine is extremely simple, the interface between the virtual machine and the player is somewhat more complicated.[10] BD+ provides the content code with 25 system calls or "traps". An overview is given in the table below. Note that the bits 00–07 of the trap id uniquely identify each trap within a group. The group id itself is specified by the bits 08–16 of the trap id. The group ids seen so far are 00 (event handling), 01 (cryptography operations), 02 (arithmetic operations), 03 (memory operations), 04 (slot memory access), 05 (device access) and 80 (debugging).

Group ID Trap ID Name Parameters
00 000010 TRAP_Finished 0
000020 TRAP_FixUpTableSend 2
01 000110 TRAP_Aes 5
000120 TRAP_PrivateKey 5
000130 TRAP_Random 2
000140 TRAP_Sha1 4
02 000210 TRAP_AddWithCarry 3
000220 TRAP_MultiplyWithCarry 4
000230 TRAP_XorBlock 3
03 000310 TRAP_Memmove 3
000320 TRAP_MemSearch 5
000330 TRAP_Memset 3
04 000410 TRAP_SlotAttach 2
000420 TRAP_SlotRead 2
000430 TRAP_SlotWrite 1
05 000510 TRAP_ApplicationLayer 3
000520 TRAP_Discovery 4
000530 TRAP_DiscoveryRAM 3
000540 TRAP_LoadContentCode 5
000550 TRAP_MediaCheck 6
000560 TRAP_RunNative 4
000570 TRAP_??? 0
80 008010 TRAP_DebugLog 2
008020 TRAP_??? ?
008030 TRAP_??? ?

Each of these system calls can be invoked by the TRAP instruction (opcode 0x39). By convention register 29 is used as the stack pointer holding the memory address of the parameters. After parameter validation the system call is executed and a return code is written to register 1. During its execution the content code performs a series of tests to verify it is being executed in a trusted environment. One of these tests involves asking the player for its certificate with TRAP_Discovery. The RSA signature of this certificate is later verified by the content code using the public key of the license administration which is (optionally in obfuscated form) also stored in the content code. Later the player is asked to sign a random message with ECDSA by calling TRAP_PrivateKey. The generated signature is subsequently verified using the player's public key stored in the previously verified certificate.

Events

The BD+ virtual machine is event-driven. Five callbacks (events) are defined by the interface which the player may invoke to notify the content code of a variety of events, including the playback of various parts of the movie, shutdown, media eject events, or player security operations. The event data is exchanged using a dedicated memory area (0x00–0x3F). TRAP_Finished is invoked whenever the content code has finished processing an event. The first event invoked is EVENT_Startup which starts the execution of the content code.

Group ID Event ID Name Parameters
00 000000 EVENT_MediaInit 1
000010 EVENT_Shutdown 1
01 000110 EVENT_TitleInit 2
02 000210 EVENT_ApplicationLayer 2
000220 EVENT_ComputeSP 3

Conversion table

Before a BD+-capable disc is mastered, random sections of the .m2ts files are overwritten by random data, effectively corrupting parts of the content. The original data is stored encrypted and obfuscated within the BD+ content code.[10] After the content code has verified the security of the execution environment, it sends a table with repair instructions (the "conversion table" or "fix-up table") to the player using the system call TRAP_FixUpTableSend. The conversion table consists of one subtable for each .m2ts file on the disc. A subtable consists of multiple, possibly empty, segments which contain the repair descriptors. Each repair descriptor then provides the raw data and the offset needed to repair a small section of a .m2ts file, replacing the corrupted part of the file with the original data.

Reverse engineering and emulation of BD+ implementations

On November 8, 2007, SlySoft announced that BD+ discs can be copied with their AnyDVD HD software.[12] This was possible because first generation BD+ titles did not check if AACS was present. This allowed a user to copy a BD to the harddrive and play it back from there using only a specific version of Cyberlink's PowerDVD (3319a), but not to transcode, otherwise manipulate the content or play it back from a burned BD-R or BD-RE. Updated versions of BD+ security code plugged this hole.

On January 9, 2008, engadgethd.com reported that Fox has stated that BD+ has yet to be compromised.[13] When asked how hi-def 20th Century Fox titles had become available online, the rep reported that the titles were available as HD DVDs in Europe.

On March 3, 2008, SlySoft updated AnyDVD HD allowing the full decryption of BD+,[14] allowing not only the viewing of the film itself but also playing and copying disks with third-party software.

On March 19, 2008, a new version of AnyDVD HD was released (6.4.0.0) that supported the full removal of the BD+ copy protection for all titles released to date.[15][16][17]

In May 2008 the Blu-ray release of Jumper introduced a modified version of BD+ security code which prevented the Slysoft AnyDVD HD software from removing BD+. This modified version was again circumvented by Slysoft several months after Jumper was initially released.

In August 2008, members of the Doom9 forum began work on an independent project to create an open-source implementation of BD+.[18]

In late October 2008, the same Doom9 members made the first working repaired BD+ movie with the previously developed open source tools,[19] and as of November 1, 2008, have created code to debug content produced for BD+'s virtual machine.[20]

On November 2, 2008, Doom9 forums announced that early (pre-May 2008) BD+ discs can be played back using open source software only.[21]

In early November 2008 multiple versions of BD+ security code were released which, according to Slysoft, may take a few months to circumvent.[22]

On December 29, 2008 Slysoft announced that AnyDVD HD 6.5.0.2 decrypts copy protection on all current Blu-ray movies.[23]

On February 13, 2009 a 4th version of BD+ security code was discovered on the movie Australia,[24] rendering Slysoft's existing AnyDVD HD software ineffective.

On March 19, 2009 Slysoft announced that AnyDVD HD 6.5.3.1 adds support for some new BD+ protection in movies, e.g. Australia, The Robe, and South Pacific.[25] Some BD+ movies were not supported by Slysoft's update, e.g. Slumdog Millionaire, The Day the Earth Stood Still, Marley & Me, and the X-Men Trilogy.[26] Since then, Slysoft has released several updates adding support for newer titles.

On October 7, 2009 support for BD+ was announced for MakeMKV, making it the second application capable of handling all BD+ discs released to date.[27]

In 2010 four other companies released software that can decrypt BD+: DVDFab Blu-ray Copy, Pavtube Blu-ray Copy, and BlindWrite.

On December 18, 2013, the VideoLAN developers released libbdplus, an open-source library for BD+ decryption. As with libdvdcss, the API allows media players to use it transparently.[28]

See also

References

  1. ^ "About SPDC". Cryptography Research, Inc. Archived from the original on 1 April 2009. Retrieved 2009-04-12.
  2. ^ BD+ re-secured, Slysoft beaten
  3. ^ Ryan Singel (February 26, 2008). "How Crypto Won the DVD War". Wired. Archived from the original on 1 March 2008. Retrieved 2008-02-27.
  4. ^ "Macrovision to Acquire Blu-ray Disc Security Technology from Cryptography Research, Inc". Archived from the original on 2007-11-21.
  5. ^ "Irdeto fights piracy with BD+ technology". OnScreen Asia. 11 July 2011. Archived from the original on 25 October 2011. Retrieved 3 October 2011.
  6. ^ Rosenblatt, Bill (7 July 2011). "Irdeto Acquires BD+ Technology from Rovi". Copyright and Technology. Retrieved 9 November 2011.
  7. ^ "Blu-ray Disc Next-Generation Optical Storage: Protecting Content on the BD-ROM" (PDF). DELL. Archived (PDF) from the original on 31 March 2007. Retrieved 2007-05-03.
  8. ^ US application 2010169663, "Systems and Methods for Detecting Authorized Players", published 2010-07-01, assigned to CYBERLINK CORPORATION 
  9. ^ BD+ Technologies LLC Archived 2007-11-06 at the Wayback Machine
  10. ^ a b c d Doom9 thread on reverse engineering
  11. ^ Doom9 thread on instruction filter
  12. ^ "AnyDVD 6.1.9.6 beta - SlySoft Forum". Archived from the original on 2007-11-09. Retrieved 2007-11-09.
  13. ^ BD+ has not been compromised, yet, Engadget HD.
  14. ^ "Press Release: AnyDVD HD now with BD+ support - SlySoft Forum". Archived from the original on 2008-12-18. Retrieved 2008-03-29.
  15. ^ "AnyDVD 6.4.0.0 - SlySoft Forum". Archived from the original on 2008-03-21. Retrieved 2008-03-19.
  16. ^ ZDNet Blogs
  17. ^ "Press Release: AnyDVD HD now with BD+ support - SlySoft Forum". Archived from the original on 2008-12-18. Retrieved 2008-03-29.
  18. ^ Finally handling BD+ - Doom9 Forum
  19. ^ [1] Finally handling BD+ - Doom9 Forum
  20. ^ Dawson, K (2008-11-01). "Doom9 Researchers Break BD+". Slashdot. Archived from the original on 7 December 2008. Retrieved 2008-11-02.
  21. ^ Doom9 forums announced that BD+ disc can be copied
  22. ^ "BD+ movies that Anydvd HD 6.4.8.4 beta may not handle properly". Archived from the original on 2008-11-06. Retrieved 2008-11-14.
  23. ^ "SlySoft defeats Blu-ray's BD+ DRM scheme again". Archived from the original on 2009-01-06. Retrieved 2008-12-29.
  24. ^ "BD+ discs that may not work properly with Anydvd HD". Archived from the original on 2011-09-30. Retrieved 2009-03-13.
  25. ^ "AnyDVD (HD) 6.5.3.1 released". Archived from the original on 2011-07-16. Retrieved 2009-03-21.
  26. ^ "More BD+ discs that may not work properly with Anydvd HD". Archived from the original on 2009-04-06. Retrieved 2009-03-25.
  27. ^ BD+ status page
  28. ^ "libbdplus". VideoLAN. 2013-12-18. Retrieved 2013-12-25.
Retrieved from "https://en.wikipedia.org/w/index.php?title=BD%2B&oldid=1092398616"