Comment #34 on issue 736 by [email protected]: No way to disable plugins using UI http://code.google.com/p/chromium/issues/detail?id=736
I'm sorry for the "me too" comment but Adobe announced a security bug in the latest Reader version which has no patch and is being actively exploited. Now the options are: * The killall switch (--disable-plugins) which is useless because not even YouTube would work (so much for HTML5 <video>) * Uninstalling Reader and using some alternative (this just moves the problem elsewhere and might not be an option for a lot of people) * Try to hunt and kill the actual plugin DLLs around the filesystem, hoping that nothing else breaks too badly The whole security focus in Chromium with all the sandboxing and other measures such as the font sanitizer is rather good but completely useless if you're going to be happily running plugins (which have attack surfaces the size of Manhattan) with no sandboxing at all and no user control. All other browsers allow plugin management, the lack of such in Chrome actually makes it the least secure browser in my opinion (not that it matters much for the average person who wouldn't bother to disable plugins though). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
