3 ms·
What a frustrating change. However it still is possible to disable (though you probably will need to do this every time chrome updates) Simply deleting the fol
by nmjohn 10y ago
What a frustrating change. However it still is possible to disable (though you probably will need to do this every time chrome updates)
Simply deleting the folder that contains "widevinecdmadapter.plugin" will effectively disable the plugin.
So, for example, on OSX using homebrew to install chrome, it'd be:
rm -rf /opt/homebrew-cask/Caskroom/google-chrome-canary/latest/Google\ Chrome\ Canary.app/Contents/Versions/58.0.2996.0/Google\ Chrome\ Framework.framework/Libraries/WidevineCdm
- deleted 10y ago[deleted]
- Sunset 10y agoYou can deny write permissions to the folder.
- mschuster91 10y agoI wouldn't try that as it will likely break the auto-updater when it tries to update the Widevine files.
- jaimex2 10y agotry it, then revert if it does break.
- Sunset 10y agoIs there something like an "overlay" FUSE fs which pretend to write what you give it but then just discards what you give it and returns the actual file when you attempt to read? To defeat checks right after writes it could return what you wrote once( or a configurable number of times) but after that just give you the original file when you read it.