On Thu, Nov 03, 2016 at 10:10:20AM +0000, James Pearson wrote:> > It shows up when I run Firefox - in both about:plugins and about:addons -> > Plugins > > If you use a central Mozilla autoconfig file setup - see, for example: > > > <https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment#Configuration> > > then you can use the following line to disable this plug-in: > > lockPref("plugin.state.librhythmbox-itms-detection-plugin", 0); > > (and similar lines to disable any other plug-in) > > James PearsonWith all the talk about deleting a packaged file or rebuilding a base package, I'm surprised no one has noticed this solution. The above is most likely the best solution. Easy to deploy through CM, won't be overwritten with package updates, and is the best for "Enterprise" customers (who deploy to hundreds or thousands of computers). I'm already using something similar to change the default home page. -- Jonathan Billings <billings at negate.org>
On 11/04/2016 05:09 AM, Jonathan Billings wrote:> On Thu, Nov 03, 2016 at 10:10:20AM +0000, James Pearson wrote: >> >> It shows up when I run Firefox - in both about:plugins and about:addons -> >> Plugins >> >> If you use a central Mozilla autoconfig file setup - see, for example: >> >> >> <https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment#Configuration> >> >> then you can use the following line to disable this plug-in: >> >> lockPref("plugin.state.librhythmbox-itms-detection-plugin", 0); >> >> (and similar lines to disable any other plug-in) >> >> James Pearson > > With all the talk about deleting a packaged file or rebuilding a base > package, I'm surprised no one has noticed this solution. The above is > most likely the best solution. Easy to deploy through CM, won't be > overwritten with package updates, and is the best for "Enterprise" > customers (who deploy to hundreds or thousands of computers). > > I'm already using something similar to change the default home page. >Thank you, that looks like what I originally was seeking - a way to blacklist the plugin. It's still a bit puzzling that there isn't a checkbox next to plugins in the Preferences pane. I gather FireFox is planning to get rid of plugin support altogether so soon it may not be an issue.
Alice Wonder wrote:> > Thank you, that looks like what I originally was seeking - a way to > blacklist the plugin. > > It's still a bit puzzling that there isn't a checkbox next to plugins in > the Preferences pane.In 'about:addons -> Plugins', there is a pull down next to each plugin that has 'Ask to Activate', 'Always Activate' and 'Never Activate' I believe the default is 'Ask to Activate' - so setting this to 'Never Activate' will effectively disable the plugin The 'lockPref' example in an autoconfig file forces 'Never Activate' without letting users change this setting> I gather FireFox is planning to get rid of plugin support altogether so > soon it may not be an issue.I believe the next ESR release (ESR 52 in March 2017) will still support NPAPI plugins - although the mainline Firefox releases after that date won't (see https://blog.mozilla.org/futurereleases/2016/07/20/reducing-adobe-flash-usage-in-firefox/) - so, I guess NPAPI plugin support will still exist in Firefox shipped by RedHat/CentOS until sometime in 2018 James Pearson
On 11/04/2016 06:00 AM, Alice Wonder wrote:> On 11/04/2016 05:09 AM, Jonathan Billings wrote: >> On Thu, Nov 03, 2016 at 10:10:20AM +0000, James Pearson wrote: >>> >>> It shows up when I run Firefox - in both about:plugins and >>> about:addons -> >>> Plugins >>> >>> If you use a central Mozilla autoconfig file setup - see, for example: >>> >>> >>> <https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment#Configuration> >>> >>> >>> then you can use the following line to disable this plug-in: >>> >>> lockPref("plugin.state.librhythmbox-itms-detection-plugin", 0); >>> >>> (and similar lines to disable any other plug-in) >>> >>> James Pearson >> >> With all the talk about deleting a packaged file or rebuilding a base >> package, I'm surprised no one has noticed this solution. The above is >> most likely the best solution. Easy to deploy through CM, won't be >> overwritten with package updates, and is the best for "Enterprise" >> customers (who deploy to hundreds or thousands of computers). >> >> I'm already using something similar to change the default home page. >> > > Thank you, that looks like what I originally was seeking - a way to > blacklist the plugin.Even with the plugin disabled, it still shows up in browser fingerprinting. Effing firefox, that's just dumb. Time to rebuild the RPM without it. Er, well, I'll wait for CentOS 7.3. Er, um, I mean branch 1611 :P