4 ms·

If it is triggered by the customizations you did in Firefox, then running a fresh Firefox in a container might help: docker run -it --rm -e DISPLAY --net=h

by mg 2y ago

If it is triggered by the customizations you did in Firefox, then running a fresh Firefox in a container might help: docker run -it --rm -e DISPLAY --net=host -v $XAUTHORITY:/root/.Xauthority -v /tmp/.X11-unix:/tmp/.X11-unix debian:12-slim Then inside the container, run: apt update apt install firefox-esr firefox

stonogo 2y ago
what is the advantage here over just running 'firefox -ProfileManager' and making a clean profile?
- theamk 2y ago
  All host info not accessible via X11 protocol is hidden, for example font list, is replaced with generic one. For even more protection, run VNC server with common resolution in the container and connect to it using VNC viewer. In this case firefox provides a super generic profile (latest debian with mesa GPU), making this browser very hard to distinguish from others. This has some downsides however: First, you cannot resize window. Second, a lot of actual bots use same config, so it might be blocked.
  - veeti 2y ago
    Isn't it suspicious bot-like behavior to only have the bare minimum fonts installed? :-)
    - ghxst 2y ago
      To be fair, Firefox out of the box prevents against font fingerprinting more than Chrome, it's considerably easier to get Firefox to run in a docker container and pass all the client side challenges than Chrome in my experience, you still have a valid point though.
  - homebrewer 2y ago
    mullvad browser is pretty much this, but without messing around with containers. One fingerprint for all users, with the same font list, resolution, canvas behavior, etc. https://mullvad.net/browser https://mullvad.net/browser
    - theamk 2y ago
      looking at https://mullvad.net/en/browser/hard-facts https://mullvad.net/en/browser/hard-facts , Mullvad browser is much more extreme: many APIs blocked, always incognito mode... I would not be surprised if this blocks some sites. the container approach on the other hand is bog-standard firefox.
- rmholt 2y ago
  OP mentioned that they run a heavily modified browser, I think it means compiled with changes - docker means stock Firefox
ghjfrdghibt 2y ago
The suggestion you should have to bend over backwards for shitty software like cloudflare is bad enough; but if you were going to surely creating a new browser profile is far easily than spinning up a debain docker image, updating it and the installing Firefox and the running it?

by mg 2y ago

stonogo 2y ago

what is the advantage here over just running 'firefox -ProfileManager' and making a clean profile?

theamk 2y ago
All host info not accessible via X11 protocol is hidden, for example font list, is replaced with generic one. For even more protection, run VNC server with common resolution in the container and connect to it using VNC viewer. In this case firefox provides a super generic profile (latest debian with mesa GPU), making this browser very hard to distinguish from others. This has some downsides however: First, you cannot resize window. Second, a lot of actual bots use same config, so it might be blocked.
- veeti 2y ago
  Isn't it suspicious bot-like behavior to only have the bare minimum fonts installed? :-)
  - ghxst 2y ago
    To be fair, Firefox out of the box prevents against font fingerprinting more than Chrome, it's considerably easier to get Firefox to run in a docker container and pass all the client side challenges than Chrome in my experience, you still have a valid point though.
- homebrewer 2y ago
  mullvad browser is pretty much this, but without messing around with containers. One fingerprint for all users, with the same font list, resolution, canvas behavior, etc. https://mullvad.net/browser https://mullvad.net/browser
  - theamk 2y ago
    looking at https://mullvad.net/en/browser/hard-facts https://mullvad.net/en/browser/hard-facts , Mullvad browser is much more extreme: many APIs blocked, always incognito mode... I would not be surprised if this blocks some sites. the container approach on the other hand is bog-standard firefox.
rmholt 2y ago
OP mentioned that they run a heavily modified browser, I think it means compiled with changes - docker means stock Firefox

ghjfrdghibt 2y ago

The suggestion you should have to bend over backwards for shitty software like cloudflare is bad enough; but if you were going to surely creating a new browser profile is far easily than spinning up a debain docker image, updating it and the installing Firefox and the running it?