Aminda Suomalainen
9b4cc804e5
The logic here is hope that it will stop offering the addon if I am following their instructions and sending them the information. Oh and I added icons |
||
|---|---|---|
| .. | ||
| policies.json | ||
| README.md | ||
Firefox policies.json
The file is pretty self-explanatory, but I prefer Chromium way of handling enterprise policies since it allows me to cut them to multiple different files per whatever I am doing.
WARNING TO LIBREWOLF USERS
This file takes priority over
/usr/share/librewolf/distribution/policies.json so don’t
apply this or a lot of LibreWolf specific customizations stops being in
force.
Extensions
They are mostly self-explanatory.
Privacy Badger
jid1-MnnxcxisBPnSXQ-eff@jetpack- Downloaded directly from EFF.
Configured to learn locally and also in incognito as opposed to only relying on vendor list. Also not display the “Welcome to Privacy Badger screen”.
See also:
- https://github.com/EFForg/privacybadger/blob/master/doc/admin-deployment.md
- https://github.com/EFForg/privacybadger/blob/master/src/data/schema.json
Search engines
Policy SearchEngines is only allowed on ESR.
But who cares? Anyway thus DuckDuckGo extension is installed by default so when testing this policy I won’t have to see Google.
Additionally it’s a lie since at least Nightly reads it too without complaining.