27
Another question about browsers :)
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Dec 2024
27 points (100.0% liked)
Privacy
32506 readers
1139 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
Excluding Chrome, Firefox and Safari means that you are now relying on some random developer to understand security and privacy and as a software developer for over 40 years I can tell you that this is a fools errand.
Don't get me wrong, the big three absolutely have privacy issues, but they can be mitigated in many different ways without compromising on security.
For example, you can force DNS requests to one of your choosing, you can run them in incognito mode, refuse cookies, run them inside user accounts without personal information, etc.
I tend to run individual instances of a browser in incognito mode and am very conscious of which tabs are open in which instance, so websites cannot steal information from other tabs.
You can even run the browser in a docker container if you're extremely paranoid (I'm on the verge)
That's precisely what I do.
Docker guest still shares a kernel with host. Use a custom OCI runtimes like kata-containers (VM) or gVisor/sydbox-oci (unprivileged application kernel) to reduce the kernel attack surface and protect against privelege escalation.
This is true.
However, I'm running trusted software, not the backyard efforts of someone randomly selected off the internet.
Additionally, the Docker container is running on a dedicated Debian virtual machine with only Docker installed.
What's of deeper concern is that all instances are running on X11 which means that they all share information via the clipboard for example.
You could set up Wayland probably. Just make sure you use GNOME (Mutter) since it is the only Wayland DE that protects the screencopy API.
So far the Wayland implementation requires embedded X11 which puts everything in the same environment again.
I've not yet discovered how to run separate Wayland screens across the network from a Docker container and I'm also not sure if either Chrome or Firefox actually support native Wayland, from memory they didn't last time I checked.
Both Firefox and Chromium support native Wayland.
Also, this might lead you in the right direction for remote Wayland apps: https://github.com/wayland-transpositor/wprs