Add policy to disable protected content playback
Reported by
ch...@chrullrich.net,
Feb 10 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Steps to reproduce the problem: 1. Decide that your users should not be able to play protected content because the EME component is a needless security risk. Also, because they're supposed to be working, not Netflix-ing. 2. Look through <https://www.chromium.org/administrators/policy-list-3> for the appropriate policy item. 3. Come up empty. What is the expected behavior? 3. Find a policy that disables protected content playback. What went wrong? No such thing. Did this work before? N/A Chrome version: 64.0.3282.140 Channel: stable OS Version: 10.0 Flash Version: In bug 686430 a content setting was added that now controls the feature. However, this setting is apparently not accessible through policy. My workaround has been to replace the "WidevineCdm" directory in the Chrome installation with a regular file, which derails any attempts by Chrome to install the thing, but this is clearly not a desirable option.
,
Feb 12 2018
Thank you. While not prioritized today, we will consider this for a future release.
,
Apr 13 2018
,
Aug 1
|
||||
►
Sign in to add a comment |
||||
Comment 1 by hunyadym@chromium.org
, Feb 12 2018Owner: blumberg@chromium.org