Hi Alex, sure. The way I've been doing it for quite some time now is as follows:
a) Create a directory "core\distribution\bundles\dsm" b) Create a file "core\distribution\bundles\dsm\chrome.manifest" c) Copy the snippet into the file and you're all set: --- snip --- # default override format # [override chrome://<package>/<part>/<file> data:text/html,] # [override chrome:// data:text/html,] override chrome://browser/content/preferences/aboutPermissions.xml data:text/html, --- snip --- You actually don't need the first three lines but I like to keep them as a reminder how to do it. I basically just override the corresponding chrome:// address with a blank page. Here are just a few more examples: # * about: * override chrome://browser/content/sync/aboutSyncTabs.xul data:text/html, override chrome://global/content/crashes.xhtml data:text/html, override chrome://global/content/plugins.html data:text/html, override chrome://global/content/aboutAbout.xhtml data:text/html, override chrome://global/content/config.xul data:text/html, override chrome://global/content/aboutSupport.xhtml data:text/html, override chrome://global/content/aboutMemory.xhtml data:text/html, override chrome://mozapps/content/extensions/ data:text/html, override chrome://mozapps/content/extensions/extensions.xul data:text/html, (...) Feel free to contact me if you need some more advice. Regards, Chris On 22 January 2016 at 08:16, Alexander Heim <[email protected]> wrote: > Hello everybody, > > > > we are currently in the process of building a Firefox V38.5.2 ESR software > package to deploy in a customer environment. To customize the Firefox > Settings we use different approaches, such as a config file with > preferences, userchrome.css and the autoconfig tool (cck2). > > > > So most of the settings we would like to have implemented we already got > working now but what we still need is the possibility to block the about > sites within Firefox, especially the "about:permissions". > > > > In earlier Versions of Firefox (36.x) it was possible to configure this > with the cck2 tool. As it seems with the latest Version of cck2 you can > only configure "about:config" to be blocked but no other config pages. > > > > Is there another way to configure the "about:permissions" to be blocked as > well? > > > > Thank you very much in advance for your help! > > > > > > Kind Regards, > > Alex > > > > > > _______________________________________________ > Enterprise mailing list > [email protected] > https://mail.mozilla.org/listinfo/enterprise > > To unsubscribe from this list, please visit > https://mail.mozilla.org/listinfo/enterprise or send an email to > [email protected] with a subject of "unsubscribe" >
_______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe"
