4 ms·
HTML have always had plugins too... this ends that. Think of EME as a slightly better sandboxed plugin with a single very small purposes... As oppose to the se
by jopsen 9y ago
HTML have always had plugins too... this ends that.
Think of EME as a slightly better sandboxed plugin with a single very small purposes... As oppose to the security horrors from Flash
- eponeponepon 9y agoIf there aren't already enterprise software firms investigating how to offer their SuperWidgetron 10000 HR system through EME in the browser, I will eat my hat. The single very small purpose will soon enough be worked around, messed with and extended to do more than it was ever "supposed" to - just look at JavaScript.
- acdha 9y agoEME offers an interface to decode audio and video stream. How is what you're talking about even possible in that context?
- zachrose 9y agoSome kind of virtual webpage that's delivered over video?
- deleted 9y ago[deleted]
- belorn 9y agoWhere is the source code of the DRM module that shows that the only thing the code do to the stream is decode audio and video? Oh, that part is not part of the open part of the standard. The super cookies, the administrative hooks into the operative system, the access to everything from the webcam to the hard drive, all that is what the EME is talking to through an interface labeled audio and video stream. A perfectly sand boxed interface. The buss transporting data from the browser to the module is not very useful as an attack surface when you full control of the module itself.
- acdha 9y agoThose are good questions – and you might find Firefox's sandboxing implementation worth study – but that's not what we were talking about. Currently there's no talk of implementing restrictions on code, etc. within browsers and it hurts the cause to spread easily disproven claims that it's happening now.