upvote

points

by anthk18 hours ago |
comments
upvoteby angry_octet13 hours ago|
next
[-]
The best is probably tor in a VM, chromium in a separate VM, javascript disabled, on a private virtual network, with a egress firewall (not just guest VM firewalls, but enable those too) that only allows traffic from a specific origin port on the tor machine. You would also want the VM to spoof the processor features and unique IDs. System time drift/offset remains a vector which is hard to deal with.

Dump the rendered window pixels out to a simple viewer. Mouse movement is still a pain to deal with, but I would default to spoofing it as moving between clicks, with some image parsing logic to identify menu traversal.

Then it should reboot the browser process regularly.

I've been waiting for someone to make a packaged 'VPC in a box' incorporating networking and linked VMs.

reply
upvoteby keepamovin4 hours ago|
parent|
next
[-]
Your idea of "dumping the rendered window pixels out to a simple viewer" with Chromium is essentially Remote Browser Isolation (RBI). If you're looking for a packaged way to do this, BrowserBox does exactly this and has a tor-run function built-in, which:

connects Chrome to a Tor SOCKS proxy and wraps all other browsing-related network calls over torsocks. It prevents local fingerprinting leaks (like this IndexedDB ordering bug) because the browser isn't running locally at all. You can host the BrowserBox instance as an onion hidden service, use it to browse over Tor, or both.

If you want to try an ephemeral "VPC in a box" style setup where the environment is destroyed after you're done, you can easily spin it up using this new GitHub action: https://github.com/marketplace/actions/browserbox (but you need a license key, obtainable at https://browserbox.io)

This is my attempt to make it easy to spin up bbx on ephemeral infrastructure that's mostly free (GitHub Actions runners are perfect).

reply
upvoteby angry_octet3 hours ago|
parent|
[-]
That's great, I'll give it a try.
reply
upvoteby anthk7 hours ago|
parent|
prev|
[-]
Links can force to pass all connections to a proxy, so a FW might be redundant. Forget almost mouse, Links can be render the page either to plain X11 or a terminal.
reply
upvoteby angry_octet3 hours ago|
parent|
[-]
I'm assuming the browser is going to be compromised at some point, for example by getting it to retrieve something without using the socks proxy.
reply
upvoteby fc417fc80211 hours ago|
prev|
next
[-]
> enforcing all connection thru a proxy in the settings (mark the checkbox)

Just use a network namespace individual pieces of software are way too easy to misconfigure.

reply
upvoteby anthk7 hours ago|
parent|
[-]
Links litteraly put your a graphical (X11) or terminal based checkbox to enable that to enforce everything through the proxy with the settings menu. Not too easy. If you are going to use Tor you shouldn't be just using Tor Browser by default neither if it enables some JS options. Firefox' base is too huge to configure so nothing ever leaks. There are too many components. A/V, WebGL, telemetry, WASM, WebRTC...
reply
upvoteby sixothree17 hours ago|
prev|
[-]
Would whonix fit that bill?
reply