search for: lockpref

...ut: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 mos...

...fox homepage to be one pointing to a particular site. > Doesn't seem to be much documentation on how to make minor changes to > the account. Lots of SELinux guidance, but nothing about default home > page, etc. > > Dave > > > > See: /usr/lib/firefox/firefox.cfg Add: lockPref("browser.startup.homepage", "http://www.example.com/path/); Google: FireFox Kiosk -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive...

While doing a browser fingerprinting survey, I was quite surprised to see I actually have a FireFox plugin installed. The culprit is /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so It appears that whoever maintains the rhythmbox RPM has chosen not to package the browser plugin separately like it probably should be. So if I have the rhythmbox RPM installed, I have the plugin.

...n 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

...t;> >> 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...

...s -> 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 NP...

I'm needing to force some settings system wide for Firefox. However, I am finding that using lockPref() in firefox.js silently fails... and causes all directives that come after it in the file to be ignored. An strace shows that it reads the firefox.js file in its entirety and then goes on about its business reading other config files and then terminates for no apparent reason. Is anyone else...

...lla 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 surpr...