Issue metadata
Sign in to add a comment
|
Allow identifiers for protected content setting missing on MD settings |
||||||||||||||||||||||||
Issue descriptionChrome Version: 57.0.2982.2 (Official Build) canary (64-bit) OS: Win10 What steps will reproduce the problem? (1) Go to chrome://settings (2) Try and find the "Allow identifiers for protected content" (3) What is the expected result? Find it somewhere under "content settings" What happens instead? Cannot find it, and searches for "protected" fail. Please use labels and text to provide additional information. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Jan 31 2017
,
Jan 31 2017
I also think we need an option to disable Widevine completely. We used to have that ability in chrome://plugins, and even if it's rarely used, I'd like to retain the ability. I don't think we have a clear, documented security bar for who/what origins can load the CDM, and hence its attack surface might be more exposed than we expect. (I'd love to be wrong; is there documentation?) Is M-57 doable?
,
Jan 31 2017
fyi: md settings is not shipping in M-57
,
Jan 31 2017
,
Feb 6 2017
tommycli@: are you already looking into something like this?
,
Feb 7 2017
Yes, I've duped this issue into the bug that fixes this for MD Settings: 687783 The main issue (that allows disabling Widevine in Old Options as well) is here, which I'm also working on: 686430 re: palmer, we're working reasonably hard to get this done, tested, and merged into 57. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by wfh@chromium.org
, Jan 30 2017