[Mozilla Enterprise] Firefox Configuration Confusion - Need to Secure Firefox

[Éric Périard]

***Typo fix*** Not my day... :/

From: Enterprise <enterprise-bounces at mozilla.org> On Behalf Of Éric Périard
Sent: Monday, September 9, 2019 7:45 AM
To: Eddie Rowe <eddie.rowe at tdhca.state.tx.us>; enterprise at mozilla.org
Subject: Re: [Mozilla Enterprise] Firefox Configuration Confusion - Need to Secure Firefox

Classification: Unclassified

Agreed, for those of us who have been managing ESR in our environment it's not too bad, but for someone just stepping into the fold, it could become a roadblock of red tape... Google's approach is consistent and the templates don't change every 5 minutes.

However, keep in mind Eddie, that Mozilla has been doing actual admx/adml templates for little over a year now, so we're sort of the guineapig in all of this.

Back then, all you had were those ini's and autoconfig files and other tools to configure FF.

At the end of the day, Mozilla is a much smaller group than Google Inc and they're doing the best they can to help out enterprise users.

Speaking of other tools, check with Mike Kaply, he's got something you may be interested in ;)

Éric Périard

Mission Network System Administrator | Administrateur de système du réseau de mission
Canadian Centre for Cyber Security | Centre canadien pour la cybersécurité
Email | Courriel: Eric.Periard at cyber.gc.ca<mailto:Eric.Periard at cyber.gc.ca>
Website | Site Web: https://www.cyber.gc.ca/
Government of Canada | Gouvernement du Canada

[cid:image002.png at 01D4ADA3.F54E4950]




From: Enterprise <enterprise-bounces at mozilla.org<mailto:enterprise-bounces at mozilla.org>> On Behalf Of Eddie Rowe
Sent: Sunday, September 8, 2019 4:28 PM
To: enterprise at mozilla.org<mailto:enterprise at mozilla.org>
Subject: [Mozilla Enterprise] Firefox Configuration Confusion - Need to Secure Firefox

Given Mozilla's decision to turn on DNS over HTTPS we have to secure Firefox to disable this type of nonsense or remove it from every PC in the next two weeks.  Chrome is configured through an easy to manage GPO which leverages other really smart people who have created a security baseline along with preconfigured GPOs, while Firefox does not seem to have this level of support.

Assuming a  person is new to Firefox, exactly what are we supposed to modify to setup things securely?  I see references to things going into Mozilla.cfg, policies.json, GPO, autoconfig.js...I probably missed a file too.  I see people helpfully answering a question and telling the person to go to https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment for the answer to their question, but there are just more links there.  I see people posting to not to bother with GPO because all the options are not there, but other say there are GPO settings that are no elsewhere... I see references that one thing is set one place, another place overrides...  I see one document say the autoconfig.js file goes into the folder where Firefox is installed, but the same document says it does into a subfolder...  I see references to setting preferences in the policies.json file, but I thought Mozilla.cfg was to be used for this?  Finally I see mention that there are preferences that are set in the source code that are not exposed to about:config?

Surely there is a simple one page document that walks you through this so we can spend a LIMITED amount of time sorting this out???

https://www.zdnet.com/article/mozilla-to-gradually-enable-dns-over-https-for-firefox-us-users-later-this-month/ - Ready or not, here comes DNS over HTTPS to bypass all security you have using DNS to block dangerous sites.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/enterprise/attachments/20190909/ff4b6f90/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 32780 bytes
Desc: image001.png
URL: <http://mail.mozilla.org/pipermail/enterprise/attachments/20190909/ff4b6f90/attachment-0001.png>