News for hackers. Stuff that matters.
Re:Chrome Widevine DRM can no longer be disabled by 0x0 on Sunday January 29, 2017 @04:05PM (#13516645)
I used to disable flash in chrome://plugins/ but starting in Chrome 56 it keeps re-enabling it there (and all the other plugins) on every launch. I still have "click-to-play-flash" set, but the result is that instead of being served a html5 player, I'm being served a blocked "click-to-play" flash player.
Re:Chrome Widevine DRM can no longer be disabled by beojan on Sunday January 29, 2017 @04:32PM (#13516823)
I have a feeling this is a bug rather than a deliberate choice, given Google are trying to encourage use of HTML5.
Re:Chrome Widevine DRM can no longer be disabled by mynameisvlad on Sunday January 29, 2017 @06:27PM (#13517473)
That, plus the "(and all the other plugins)" really signals that this is unintended. Something probably isn't reading or writing the setting to the right place, and it's just being enabled by default.
Re:Chrome Widevine DRM can no longer be disabled by cpeterso on Monday January 30, 2017 @12:37AM (#13518946)
I just updated from Chrome 55 to 56 and saw the same thing in chrome://plugins. I guess Google's position is that click-to-play Flash is the same as disabled Flash because the plugin doesn't run without user action.