4 ms·
I agree that would be a problem, but I understand there would be a way to implement the current proposal without requiring a browser to be closed source. https
by gph 14y ago
I agree that would be a problem, but I understand there would be a way to implement the current proposal without requiring a browser to be closed source.
https://news.ycombinator.com/item?id=5232033 https://news.ycombinator.com/item?id=5232033
https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/encrypted-media.html https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med...
It's not a perfect method, it would require some additional potentially closed-source OS-level software to be installed for the browser to interact with. But people who don't want it don't have to get it, and the browser can implement the standard without becoming closed-source.
- rb12345 14y agoThat's also true, but as you point out, still requires a closed-source or a hardware DRM decoder to avoid kernel-level attacks. That would seem to rule out Linux support even if Windows or OS X Firefox/Chrome can safely use it.