[encrypted-media] EME is undermines its stated purpose

GravisZro has just created a new issue for 
https://github.com/w3c/encrypted-media:

== EME is undermines its stated purpose ==
It's stated in the abstract that the EME purpose it for "providing 
APIs to control playback of protected content" but a standard (open) 
API undermines all content protection schemes using it thereby 
defeating its reason for existing.

There are a couple ways this can manifest:
- If the protected content, CDM, license requests/responses are all 
written to disk by the browser then they can be packaged into a single
 file for later playback.
- The CDM is architecture and OS agnostic, so it cannot make direct 
rendering calls.  As a result, any possible output from the CDM can be
 recorded to disk as an unprotected media format.

(sidenote: W3C members like Netflix have "promised" to not prosecute 
program authors therefore, content owners (e.g. Warner Bros.) will be 
prosecuting people that implement EME in a way that allows you to save
 content for later viewing under a DMCA violation claim.)

However, regardless of the reaction content owners have, the core 
purpose of this API is impossible to fulfill because it's paradoxical.
  You cannot have a standard and open API for protected content 
because doing so intrinsically removes the protections.

Please view or discuss this issue at 
https://github.com/w3c/encrypted-media/issues/156 using your GitHub 
account

Received on Thursday, 7 April 2016 16:38:47 UTC