Hacker News Reader

DRM is based on obfuscation at the core. How would this ever work with open source browsers?

It wouldn't. The explicitly stated plan from the people who originated this proposal involves proprietary browser plugins.

Not necessarily browser plugins. Could be browser or OS or hardware.. Each website has control over what DRM it accepts, which leads to a world where hardware eventually becomes the requirement.

Regardless if it's technically a plugin or part of the OS accessed through a bridge, or anything else, EME fundamentally depends on proprietary code (and that code will not be part of any open source browser).

Then it would only be a matter of hacking one browser to claim to support drm scheme x and then not to get it to work. Since we have to distribute the run time in at least one browser, this shouldn't be a problem.

Do you have any clue how encryption works? There are plenty of open-source encryption algorithms that are very secure.

I'm not sure how W3C is recommending the DRM be implemented, but it is in no way necessary for the source code for browsers to be 'closed' vs 'open' source in order to have effective DRM.

Reply on news.ycombinator.com