News for hackers. Stuff that matters.
Re:Web DRM moves to next phase, Defective by Design to conti... by RBO2 on Thursday July 07, 2016 @05:24AM (#12048314)
W3C did this move because its biggest sponsors are the DRM makers (Google, Microsoft).

To make it acceptable they made it optional. But in practice all major browsers implemented it.

The right answer is now to standardized the W3C CDM black box by standardizing DRMs as ETSI has started (https://lists.w3.org/Archives/Public/public-html-media/2014F...). W3C should contribute to this effort.

Useful link on EME: https://www.w3.org/2016/03/EME-factsheet.html

Re:Web DRM moves to next phase, Defective by Design to conti... by hsivonen on Thursday July 07, 2016 @09:44AM (#12049241)
The ETSI thing doesn't solve problems. It creates a layer of abstraction that in theory makes the key acquisition protocol defined by whatever runs on the ETSI layer, but now you have the problem of remotely attesting the tamper-resistance of the ETSI layer itself. It would make more sense to standardize the protocol than to define an execution environment for arbitrary protocol engines.
Re:Web DRM moves to next phase, Defective by Design to conti... by RBO2 on Thursday July 07, 2016 @01:03PM (#12050608)
Agreed. That's one of the reason why this initiative stalls. However the back idea is to standardize a DRM protocol that would be accepted by the copyright owners and that's a step in the right direction.