Re:On Encrypted Media Extensions (EME) in HTML5
by BinaryIdiot on Wednesday March 01, 2017 @07:38PM
(#13770257)
This echos my original feelings. But if I understand correctly if you find a vulnerability in the extension and report it, you can be sued. There is no protection from users doing anything with EMEs other than letting them run.
I believe that is the case, anyway.
Re:On Encrypted Media Extensions (EME) in HTML5
by azakai on Wednesday March 01, 2017 @10:15PM
(#13771118)
It's more like standardizing a road that only Google, Microsoft and Apple and their partners can drive on.
An open standard is one that anyone can implement. EME is not open in that way - it just standardizes a small part, the interface. The DRM itself remains completely nonstandard, and Google, Microsoft, Adobe etc. all have their own proprietary DRM products. So a browser that actually wants to show EME content must partner with them. That's the opposite of an open standard.
This at least standardizes the process. Perhaps that's a bit like standardizing the roads we drive on: it gets people around and enables commerce, but the long term trade-off might be too much.