[Bug 21081] Analysis of open source DRM systems and features that could be adopted

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21081

Henri Sivonen <hsivonen@iki.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hsivonen@iki.fi

--- Comment #1 from Henri Sivonen <hsivonen@iki.fi> ---
(In reply to comment #0)
> OpenIPMP:
> http://sourceforge.net/projects/openipmp/

FWIW, I think this one isn't particularly interesting to analyze. It says it's
an implementation of OMA DRM and it explicitly warns about 3rd-party patent
claims. If the exact values of certain private keys are withheld, it's not
suprprising that you can publicly specify a Key System and show its source code
if it depends on Tivoization for robustness.

In general, being able to show source code excluding a private key or two is
not much of a trick if the code runs on a Tivoized system.

On the technical level, designing a Key System for streaming use cases is a
back-of-a-napkin exercise. 

The things that are the true obstacles:
 * Patents starting with H.264 royalties if a design where elementary streams
don't leave the CDM is a requirement.
 * Software-only CDMs on general-purpose computers depend on obfuscation of the
object code and its run-time memory and tooling for Hollywood-grade obfuscation
does not appear to be available as Open Source.
 * Inability to allow end users to build a compatible software-only CDM binary
from source. (This breaks down to two things: having to hand over the private
keys for true compatibility and robustness depending on the user not having
built the CDM box themselves.)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 22 February 2013 08:14:40 UTC