3 ms·
> EME unblocked killing Flash and made the web more secure. Neither of these are correct. Flash was dead on mobile long before EME, and the code running behind
by mmastrac 4y ago
> EME unblocked killing Flash and made the web more secure.
Neither of these are correct. Flash was dead on mobile long before EME, and the code running behind EMEs is an unaudited, black box (and having worked on decompiling the Mediatek secure enclave code, it's absolutely horrendous).
The only thing I'd consider to be marginally secure is Firefox's sandboxed DRM provider, and that could easily be a vendored extension on the window/media object.
- shadowgovt 4y ago> the code running behind EMEs is an unaudited, black box It's an unaudited black box that isn't running in the same process as the browser itself. It can certainly do risky things in that context, but one of those things isn't "scrape the user's bank password directly out of the RAM it's sharing with the tab showing the bank's web site."
- mmastrac 4y agoI'm not going to defend plugins as they were (a plugin-based DRM solution would not necessarily rely on the <embed> tags), but they were migrating to run in sandboxes before flash died. Chrome shipped flash-as-locked-down-process from early in its history. EME code, however, can have deep hooks into the OS, especially on mobile.