4 ms·
The CDM may render directly to the underlying platform; it doesn't have to pass decrypted content back to the browser for rendering. Seriously though, everyone
by cheald 13y ago
The CDM may render directly to the underlying platform; it doesn't have to pass decrypted content back to the browser for rendering.
Seriously though, everyone should go just read the spec. Or at the least, take a looksee at this: https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-media/stack_overview.png https://dvcs.w3.org/hg/html-media/raw-file/tip/encrypted-med...
- PeterisP 13y agoYes, and the underlying platform (OS) can cooperate with the browser to allow easy one-click saving of the rendered data after it's been rendered. Unless the whole stack from hardware through to the DRM plugin is locked down.
- cheald 13y agoCertainly, but that's always true of every non-trusted computing platform. You can do that with Flash or Silverlight or any other video DRM system today. I rather suspect it's a very big part of the reason that CDMs don't get published for Linux, because it would be trivial to modify the system to just jack the content on its way out to the display.
- toyg 13y ago> Unless the whole stack from hardware through to the DRM plugin is locked down. Which is why you have TPM and the various Microsoft/Apple/Google DRM schemes: Hollywood wants to lock down the full stack, and they're getting there one piece at the time. For TPM, their enabler was Microsoft and their desire to lock down the boot process to enforce licensing. For this spec, it's Google and Netflix because they think it's the only way their media services will survive in the long run. Insert here smart quote about expert frog-boiling.