Re:W3C abandons consensus, standardizes DRM, EFF resigns
by jayshua on Monday September 18, 2017 @05:35PM
(#15279823)
What makes EME a malware interface?
[ Parent
| on HN ]
Re:W3C abandons consensus, standardizes DRM, EFF resigns
by wolfgke on Monday September 18, 2017 @05:40PM
(#15279885)
DRM is malware (I don't seriously believe I have to explain why) - so EME is a malware interface.
Re:W3C abandons consensus, standardizes DRM, EFF resigns
by jayshua on Monday September 18, 2017 @05:47PM
(#15279942)
I'm completely unfamiliar the entire discussion (I've just ignored it in the past), and I don't actually know why you think that. Could you elaborate?
Re:W3C abandons consensus, standardizes DRM, EFF resigns
by imtringued on Monday September 18, 2017 @08:43PM
(#15280938)
A EME module is basically a proprietary closed source plugin just like silverlight and flash and shares the same potential security issues.
Re:W3C abandons consensus, standardizes DRM, EFF resigns
by acdha on Tuesday September 19, 2017 @06:06AM
(#15283186)
That's a gross oversimplification: Flash and Silverlight were rich platforms with complexity on the same order as the entire browser. EME has a much narrower interface which provides stream decryption – it doesn't even have the video codec, whereas Flash/Silverlight had complex video, audio, image, PDF, font, etc. implementations with a long history of exploits.
This really matters because so many of those exploits relied on other features to actually run the payload. Not having any of those in the first place is a big attack surface reduction, even if the politics are legitimately debatable.
Re:W3C abandons consensus, standardizes DRM, EFF resigns
by Dylan16807 on Monday September 18, 2017 @07:31PM
(#15280609)
It makes your computer stop responding to your commands in a bunch of ways.