3 ms·

You may be right about minimizing the permissions given to CDM plugins. In the current Chrome dev build, the Widevine CDM plugin is a Pepper plugin, which sugge

You may be right about minimizing the permissions given to CDM plugins. In the current Chrome dev build, the Widevine CDM plugin is a Pepper plugin, which suggests that it might be sandboxed. However, DRM has sometimes been very over-reaching. Perhaps the most infamous example of this was the content protection introduced in Windows Vista, which went very deep into the OS. [1] After that, can we really expect that DRM proponents would be satisfied with letting their content "protection" system be a well-behaved, harmless little program inside a sandbox? [1] http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html

greggman 13y ago
Being a Pepper plugin doesn't help at all. It's still a black box. It still has full access to your machine. It can not be sandboxed because it's up to the CDM to decide how to validate and how deep to connect to the machine. The CDM will want to control the bits from the time they get delivered to the CDM from the browser, all the way to the monitor with whatever tech the CDM author feels like employing. Chrome can not validate the code nor the inputs to the code. It's a giant security hole. For all you know some CDM will just implement the blu-ray standard, Java and all. Yep, unsecured code execution.