Comment

qwert230839265026494@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

I’ve been enjoying your responses a lot! I just wanted to express my gratitude one more time!

Uhmm…, but I think that somewhat of a misunderstanding might happened somewhere.

Valid response, but why do you need to protect the OS from the browser when the browser (Brave) is already sandboxing and the browser is not an attack vector that can be directly exploited to gain access/root on your OS?

Just to be clear. I acknowledge Brave’s (or rather Chromium’s for that matter) sandbox capabilities. I’m not necessarily afraid of whatever I’m doing inside to break out of the sandbox. Sure, the ‘risk’ (if at all) can be further circumvented with the use of VMs and whatnot and for some people this approach is justified. But me lamenting on using something like Qubes (eventually) is more about having an OS that actually has sane security defaults. And having browsers run in VMs is just part of that. Currently, I just want a secure and private browser to use on desktop. So far, it seems that Brave is superior over Chromium due to added features like fingerprint-spoofing, the inevitable discontinuation of Manifest v2 etc.

What I am afraid of is how secure (continued) operation within containers would be. So even if Brave (or whichever browser for that matter) is not the culprit, the rest of the container environment might endanger the rest of my system. Of course, I’m a total noob so I might be talkin’ outta my A$$. So please correct me if my understanding is faulty.

So unless you are downloading files from very questionable locations I can’t see the need for a containerised browser.

Hehe, I guess if I would be forced to do a thing like that I would do so within a VM 😅.

Containers are good and yes have flaws but the main purpose of them is to add another layer between the application and the OS so if application is exploited the attacker has to break another wall/layer to get to the real root.

So I’ve mostly been using well-integrated ‘pet-containers’ like the ones known from Distrobox (with a relevant recent feature). Aside from those I’ve been exposed to the earlier article and to this video. These ‘expositions’ have made me go from a Distrobox-enjoyer to a pessimist that doesn’t dare to come close to them until I’ve better educated myself on them 🤣.

source

Sort:hotnew top

t0m5k1@lemmy.world ⁨1⁩ ⁨year⁩ ago

I’ve been enjoying your responses a lot! I just wanted to express my gratitude one more time!

Thanks man, means a lot these days.

What I am afraid of is how secure (continued) operation within containers would be. So even if Brave (or whichever browser for that matter) is not the culprit, the rest of the container environment might endanger the rest of my system.

If your container for brave is running but the browser itself is closed, there is no way for to happen within the container because the software that would be connected to the internet is closed/quit/stopped. In fact that container should be reported as down by whichever management subsystem is provided by said container (portainer, lxd, systemd-namespaces, etc)

So I’ve mostly been using well-integrated ‘pet-containers’ like the ones known from Distrobox (with a relevant recent feature). Aside from those I’ve been exposed to the earlier article and to this video. These ‘expositions’ have made me go from a Distrobox-enjoyer to a pessimist that doesn’t dare to come close to them until I’ve better educated myself on them

I think you should look more into what containers are and can do, You previously said that your system is low power but distrobox is making loads of of full OS/distro containers which for the most part act like a VM. Distrobox is a good way to test drive a distro OR allow a dev to ensure the app they’ve made works on their target distro’s for chosen use case.

All you really need to do is run a single application within a container, not a whole distro!/os Why do I say this? Well resource consumption for one and why replicate an entire distro/os when an app can be run inside a container: bacchi.org/posts/brave-in-docker/

Additionally I spoke about attack vectors, running another distro/OS inside a docker may well have samba, ssh running by default, If the container for that is not firewalled that is is an attack vector that will allow RCE and exploits be run inside that container!

Aside from those I’ve been exposed to the earlier article and to this video.

The first minute of that video talks of nginx webserver image, That is a webserver running inside a container, with distrobox you have the rest of the OS inside the container as well as nginx. Do you get what I say now?

I suggest you use the above link I gave to look into running just a browser within a container, drop distrobox (unless you need to test drive distros) and learn about running a single application within a container, when you can do that find a container framework that provides the security you want/like then run your “untrusted” applications in containers and rejoice with a slightly faster machine.

source
- qwert230839265026494@sh.itjust.works ⁨1⁩ ⁨year⁩ ago
  You’ve made my day. Thank you so much!
  
  All you really need to do is run a single application within a container, not a whole distro!/os Why do I say this? Well resource consumption for one and why replicate an entire distro/os when an app can be run inside a container: bacchi.org/posts/brave-in-docker/
  
  Mind-blown. I was already thinking for such a long time that the distrobox approach just didn’t seem right at all for the purpose of security. But somehow my limited search never bear any results on how I should go about it. Perhaps I didn’t do a good job on googling or somehow missed a (couple of) keywords to be effective at searching for this. And I seem to have finally found ‘the holy-grail’; for which all credits obviously go to you!
  
  Additionally I spoke about attack vectors, running another distro/OS inside a docker may well have samba, ssh running by default, If the container for that is not firewalled that is is an attack vector that will allow RCE and exploits be run inside that container!
  
  Exactly!
  
  The first minute of that video talks of nginx webserver image, That is a webserver running inside a container, with distrobox you have the rest of the OS inside the container as well as nginx. Do you get what I say now?
  
  Yup (or at least I hope so :P ). And I would have loved to share the feeling of my head/brains right now. Just bliss for finally finding the missing piece that has been (somehow) absent all this time.
  
  I suggest you use the above link I gave to look into running just a browser within a container, drop distrobox (unless you need to test drive distros) and learn about running a single application within a container, when you can do that find a container framework that provides the security you want/like then run your “untrusted” applications in containers and rejoice with a slightly faster machine.
  
  I will definitely! Are there any keywords beyond the ones mentioned in your excellent comments that I would need for an endeavor as such?
  
  EDIT: Additionally wolfi is based on Alpine, This is a popular server distro, If you want to install wolfi you’ll need to know how to install alpine, which is similar to installing gentoo as it uses bootstrap images, don’t be surprised if the desktop experience is a bit …erm lacking as that is not the focus of alpine or wolfi ! Good luck
  
  Wolfi was only mentioned as a ‘safer’ distrobox-container. It’s the only one accessible through Distrobox that I’m okay with using 😅.
  
  Words can’t describe the epiphany I’m currently experiencing! Thanks again so much! I wish you and your loved ones the best! Heck, I would be fine with buying you a beer (or a cup of coffee :P ) or whatever. Please feel free to make use of ‘these services’ :P .
  
  source
  - t0m5k1@lemmy.world ⁨1⁩ ⁨year⁩ ago
    
    Mind-blown. I was already thinking for such a long time that the distrobox approach just didn’t seem right at all for the purpose of security. But somehow my limited search never bear any results on how I should go about it. Perhaps I didn’t do a good job on googling or somehow missed a (couple of) keywords to be effective at searching for this. And I seem to have finally found ‘the holy-grail’; for which all credits obviously go to you!
    
    TBH I don’t use google search as all the results are there by SEO and algorithms, If I need a file type on a site …then it’s a different matter lol. I use DDG mainly and all I searched for was “brave browser in a container”
    
    For more take a peak here: hub.docker.com
    
    I will definitely! Are there any keywords beyond the ones mentioned in your excellent comments that I would need for an endeavor as such?
    
    I’d suggest following a good guide for your OS to get a container framework running say docker (seeing as I linked to the hub there): docs.docker.com/engine/install/fedora/
    
    Once the “Engine” is installed move on to the next sections to learn how to use it, bear in mind you really don’t need to make your own repo or pay a subscription as what you want is already out there provided by others.
    
    Once you get things working and you have an application working in docker go check out the sites for the apps you use, check their github repos and you might find links to “Docker image” and then that means you can plonk it in a container, job done. For the applications you can’t easily find an image for consider going deeper and making your own, just follow the other examples you’ve used and to share them open a repo on github or gitlab.
    
    source