Added additional Browser-Extensions & -Policy's

[Chickenbreadlp]

I added The Browser Extensions HTTPS Everywhere & The Great suspender for safety and performance respectively and also added Dark Reader as an allowed Plugin. I would've pre-installed Dark-Reader as well, if it wouldn't automatically engage. Dark Reader can break websites, and because of that I wouldn't leave it enabled by default.

I also added a few policies about Autofill and Browser-Users. Autofill and multiple Users aren't required so I disabled them, and I also disabled the browser-wide Google login.

[darnfish]

This looks good! At the moment we're trying to not install too much in terms of extensions on the VM instances, so if the extensions could possibly be moved to a README.md file where users could look at recommended extensions and then add them on their own accord, I'd be happy to merge this in. Thanks for your contribution!

[JeDaYoshi]

Honestly I think uBlock Origin and HTTPS Everywhere is more than enough.

[Chickenbreadlp]

Would this be OK for the Readme?

--- Snip --- Use yarn docker:build to build an image for deployment in production.

Chromium Extensions

Installing Extensions

To install Extensions into the Chromium Webbrowser of your Cryb instances, add the ID of the Extension in Question to configs/chromium_policy.json under "ExtensionInstallWhitelist" and "ExtensionInstallForcelist". The new Extension should now be installed by default.

Recommended Extensions

Here are a few Extensions recommended in certain Use-Cases:

Name	ID	Chrome Webstore Link	Recommended Use-Case
The Great Suspender	klbibkeccnjlkjkiokjodocebajanakg	https://chrome.google.com/webstore/detail/the-great-suspender/klbibkeccnjlkjkiokjodocebajanakg	This can improve performance, if your Cryb instances have unused tabs running in the background for hours on end
Dark Reader	eimadpbcbfnmbkopoojfekhnkhdbieeh	https://chrome.google.com/webstore/detail/dark-reader/eimadpbcbfnmbkopoojfekhnkhdbieeh	Adds Dark Mode to Websites, that don't have one. Has the potential to break Websites

Questions / Issues

--- Snip ---

[JeDaYoshi]

I honestly don't like the idea of suggesting to edit the Chromium policies file though. Future commits could break changes.

[Chickenbreadlp]

I honest to god don't know how to implement that into the .env file. I know NodeJS, but I don't know it that well ^^"
I can look into it though

[JeDaYoshi]

No way of doing so unless we generate the JSON on-the-fly with a script though.

[Chickenbreadlp]

I've been thinking about how to still use the current config JSON, while adding something on-the-fly. And my Idea would be to use a lightweight bash script, or better a lightweight NodeJS script, to modify the config JSON after copying it. I'll be looking into implementing this, when I get home

[Chickenbreadlp]

I would continue work on the "load extensions from .env", but I can't seem to get docker running on my Windows machine today -.- If anyone on the team can take this over to get it done earlier, that would be fine by me. Then you may merge this ^^

[JeDaYoshi]

Sorry this never got merged!