docker-firefox VS I-Dont-Care-About-HSTS-For-Localhost

Here's a Firefox version. It won't be any better for quality/performance though. https://github.com/jlesage/docker-firefox

I use Apache for my primary web server accessed through 80/443, and I need to set up a reverse proxy to a Docker container. Specifically, I'm trying to set up a reverse proxy for this Firefox image so I can use it on the go.

There was a project on here a while back where you could basically host a Firefox instance on a VPS somewhere and use it over the web (reddit post about it). It was pretty cool. It was for use for things like private browsing anywhere you want. Something like that could push Orb into an area where it would be useful for folks with use-cases like that, and not just people with NAS/servers to manage.

I have setup Firefox docker that I can access from my nginx server. It's just normal https traffic so won't be blocked in a corporate environment. You might want to firewall it off from the rest of your network somehow and definitely add access controls to it. Works surprisingly well though

But let me clarify my question: let's say I'd like to run Firefox on docker and would need to be able to access it remotely. I could use a pre-built image like docker-firefox. But how can I verify that the Firefox that's included in this image has not been tampered with? Is there a way? If not, is there a (simpl-ish) way to download Firefox off mozilla.org and put it in a docker container together with a remote desktop server or a web server? Or would a simple Linux VM be the easier way?

The Firefox image (https://github.com/jlesage/docker-firefox/blob/master/Dockerfile) then installs Firefox, fonts and other tools.

I want to create docker image of Ungoogled Chromium, with a webUI for accessing the browser, similar to QNAP's Browser Station and this docker image of firefox.

This —- I really don’t care if my blog with no user registration or comments gets accessed over HTTP/1.1 without an SSL cert. Further, I find the way Chrome handles HSTS pretty gross, as some of us actually tinker with stuff that REALLY doesn’t need encryption, like little dev boards and projects running locally. Chrome makes those exceedingly difficult to use, thus the need for extremely convoluted workarounds like https://github.com/ip2k/I-Dont-Care-About-HSTS-For-Localhost (it’s my repo).

Even more ridiculous IMO is the requirement for a REAL AND VALID SSL CERT for localhost. I made https://github.com/ip2k/I-Dont-Care-About-HSTS-For-Localhost to share some of the frankly ridiculous techniques required to work around this in temporary and more permanent ways.

I don't care about HSTS for localhost\ (78 comments)