Self Protecting Digital Content ( SPDC ), is a copy protection ( digital rights management ) architecture designed by Cryptography Research, Inc . for Blu-ray discs.
16-648: SPDC has multiple meanings, including: Self-Protecting Digital Content Shell Petroleum Development Company of Nigeria State Peace and Development Council , the military regime of Myanmar (also known as Burma) Spontaneous parametric down-conversion , a process in quantum optics Social Policy and Development Centre , an economic policy research institution in Pakistan Steorn Private Developers Club Scholarship Programme for Diaspora Children ,
32-402: A constrained resource – so much so that developers typically sacrificed efficiency (processing speeds) just to make program footprints small enough to fit into the available RAM. For example, Sun Microsystems brought out a version of its Java Virtual Machine (JVM) for such constrained devices; it goes by the name of KVM . The KVM works on platforms where memory is in kilobytes as opposed to
48-476: A digital file. The presumption is that re-encoding is lossy, but fully digital copies can be made with modified viewing devices. For example, adapters which strip HDCP and output unencrypted DVI can re-encode digital copies without modifying players. Adapters can also split an HDCP-protected stream into non-encrypted DVI and S/PDIF streams, allowing for almost lossless reconstruction of digital copies with complete video and audio streams. Copies can also be made through
64-512: A licensed player before that content has been re-encrypted for transport across the wire, allowing a modified player to be used as a decryption device for protected content. Only one such device must exist for the content to be widely distributed over digital networks such as the Internet . The final weakness of all DRM schemes for noninteractive works is the ultimate decryption for display to end-users. The content can at that time be re-encoded as
80-635: A scholarship given by the Indian Government to the People of Indian Origin and NRIs. Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title SPDC . If an internal link led you here, you may wish to change the link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=SPDC&oldid=970531662 " Category : Disambiguation pages Hidden categories: Short description
96-566: Is different from Wikidata All article disambiguation pages All disambiguation pages Self-Protecting Digital Content SPDC executes code from encrypted content on a Blu-ray player . When releasing new discs, content providers can update the code, adding protections against previous circumvention methods. DRM systems in which keys for encryption and decryption do not change can be attacked with one compromised key, allowing decoding of all content using that key. SPDC attempts to keep future content protected by allowing changes to
112-582: Is loaded indirectly when a Java application launches. In addition, on most operating systems, disk files opened by an application too are read into the application's address space, thereby, contributing to its footprint. During the 1990s, computer memory became cheaper and programs with larger memory footprints became commonplace. This trend has been mostly due to the widespread use of computer software, from large enterprise-wide applications that consume vast amounts of memory (such as databases ), to memory intensive multimedia authoring and editing software. To tackle
128-794: The analog hole . Memory footprint Memory footprint refers to the amount of main memory that a program uses or references while running. The word footprint generally refers to the extent of physical dimensions that an object occupies, giving a sense of its size. In computing, the memory footprint of a software application indicates its runtime memory requirements, while the program executes. This includes all sorts of active memory regions like code segment containing (mostly) program instructions (and occasionally constants), data segment (both initialized and uninitialized), heap memory , call stack , plus memory required to hold any additional data structures, such as symbol tables , debugging data structures , open files, shared libraries mapped to
144-473: The DRM in new releases when an existing DRM method is circumvented. If a method of playback used in previously released content is revealed to have a weakness, either by review or because it has already been exploited, code embedded into content released in the future will change the method, and any attackers will have to start over and attack it again. If a certain model of players are compromised, code specific to
160-454: The current process, etc., that the program ever needs while executing and will be loaded at least once during the entire run. Larger programs have larger memory footprints. An application's memory footprint is roughly proportionate to the number and sizes of shared libraries or classes it loads, whereas static libraries, executable programs and static data areas contribute to a fixed (constant) portion. Programs themselves often do not contribute
176-603: The ever increasing memory needs, virtual memory systems were introduced that divide the available memory into equally sized portions and loads them from " pages " stored on the hard-disk on an as-and-when required basis. This approach to support programs with huge-memory-footprints has been quite successful. Most modern operating systems including Microsoft Windows , Apple's macOS , and all versions of Linux and Unix provide virtual memory systems. Traditionally, low-memory-footprint programs were of importance to running applications on embedded systems where memory would often be
SECTION 10
#1732772434825192-442: The fingerprint of a specific player. If an entire class of players is compromised, it is infeasible to revoke the ability to use the content on the entire class because many customers may have purchased players in the class. A fingerprint may be used to try to work around this limitation, but an attacker with access to multiple sources of video may "scrub" the fingerprint, removing the fingerprint entirely or rendering it useless at
208-441: The largest portions to their own memory footprints; rather, structures introduced by the run-time environment take up most of the memory. For example, a C++ compiler inserts vtables , type info objects and many temporary and anonymous objects that are active during a program's execution. In a Java program, the memory footprint is predominantly made up of the runtime environment in the form of Java virtual machine (JVM) itself that
224-444: The model can be activated to verify that the particular player has not been compromised. The player can be "fingerprinted" if found to be compromised and the information can be used later. Code can be inserted into content ( digital watermarking ) to add information to the output that specifically identifies the player, and in a large-scale distribution of the content, can be used to trace the player ( traitor tracing ). This may include
240-420: The players being emulated. Once the emulated execution environment has decrypted the content, it can then be stored in decrypted form. Because the content encryption scheme (such as BD+ ) is separate from the transport encryption scheme (such as HDCP ), digital content is transferred inside the player between circuits in unencrypted form. It is possible to extract digital data directly from circuit traces inside
256-453: The very least. Because dynamic execution requires a virtual environment , it may be possible to recreate an execution environment on a general purpose computer that feeds the executing code whatever an attacker wants the code to see in terms of digital fingerprints and memory footprints . This allows players running on general purpose computers to emulate any specific model of player, potentially by simply downloading firmware updates for
#824175