On 11/06/2016 03:39 PM, Leon Fauster wrote: > Am 06.11.2016 um 18:37 schrieb Alice Wonder <alice at domblogger.net>: >> 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: >>>> >>>> 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 > > > as already suggested - build your own meta package with trigger scripts, to address future updates. > Actually kind of just thinking of putting something in cron.hourly to remove it. Easier to debug if it doesn't work. KISS.