• 2 Posts
  • 23 Comments
Joined 9 months ago
cake
Cake day: September 21st, 2023

help-circle

  • 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: https://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 .




  • 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 have 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 🤣.



  • Thanks a lot for mentioning this! I didn’t know someone took over the good work from Bromite. I’ll definitely check into it! Am I correct to assume that (like Bromite), this is a browser exclusively meant to be used on Android devices? I guess I might get it to work on Waydroid as well, not sure if I would like to commit to that yet though. Nonetheless, this input of yours has been much appreciated!



  • Your help is much appreciated!

    Question: Why do you think need such high security for a browser?

    Good prompt! I actually started questioning my own motivations from this. And I’d say that the best I could come up with was that it’s required in order to attain the “peace of mind” from having properly secured my browser activity; which happens to be the primary activity on my device anyways.




  • Man you’ve gone down a security worm hole that makes me wonder if you should really be running qubes-OS rather than Fedora 🤣.

    Hahaha 🤣. Honestly I would, if my device could handle.

    Seriously if you need more than the chromium sandbox for brave and want simplicity just use firejail.

    Madaidan strikes (yet) again. F*ck my paranoia…

    The article you linked to is a wonderfully detailed write up but it is more geared towards those using containers that will be providing services (web, sql, etc) if you just want a browser in a secure container then any of the implementations will be fine for you. The browser is not a vector used to gain access to your OS directly but what you download potentially is so with that in mind your downloads folder should really be a CLAMFS folder or a target folder for on-access scanning by clamav.

    Very interesting insights! Thank you so much! Would you happen to know of resources that I might refer to for this?



  • I believe Brave is the most private chromium browser, at least with the installation defaults.

    I haven’t come across anything that surpasses its defaults yet within the realm of Chromium-based browsers.

    As for the controversies with the company, there were some at the beginning stages, but I haven’t heard anything new in quite a while.

    Like I said in the original post, those would be secondary reasons after their respective merits in security and privacy had been resolved to a tie. Though, so far, Brave seems to be the clear winner. I would like to thank the Privacy Guides community over at lemmy.one for their engagement and contributions for that*.

    Regarding the crypto, vpn, etc bloat, I use Brave on all my devices and all I have to do is hide that stuff after the installation and I’ve never been bothered by pop-ups or similar annoyances. I don’t think it’s more annoying to remove than Firefox with the recommended sites and Pocket.

    Yeah, the linked article by Privacy Guides in the original post already shows what should be applied. Some kind of hardening seems to be done first by default anyways, it seems*.

    Since you want private browsing, I would also say that a big plus for Brave is that it has built-in Tor browser.

    For whatever it’s worth, the Privacy Guides team is against using it:

    “Brave is not as resistant to fingerprinting as the Tor Browser and far fewer people use Brave with Tor, so you will stand out. Where strong anonymity is required use the Tor Browser.”



  • on other Linux distros the way to get brave is via flatpak if the provided repos are borked for you.

    I would love to use the flatpak if it was endorsed. Privacy Guides says the following about it:

    “We advise against using the Flatpak version of Brave, as it replaces Chromium’s sandbox with Flatpak’s, which is less effective. Additionally, the package is not maintained by Brave Software, Inc.”


  • Chromium vs Brave? Firefox.

    “Just use Firefox/Librewolf or any other privacy-conscious browser that isn’t Chromium-based.” I already do, but some websites/platforms don’t play nice on non-Chromium-based browsers due to Google’s monopoly on the web. Sometimes I can afford to not use that website/platform, but unfortunately not always.

    😅. Thanks anyways 👍.


  • I mentioned Brendan specifically because people like to lump in his flaws as reasons for not using brave in these discussions.

    True. His name didn’t stick with me as his controversies and the fact that he is co-founder and CEO of Brave weren’t necessarily reasons I would forego Brave for. Feelings have to be put aside IMO in favor of merits.

    Firefox used to have xulrunner and prism to provide them but now Firefox doesn’t provide a way other than a JavaScript popup via bookmarklet.

    It’s really unfortunate that Firefox did this. This is actually one of the reasons why I like to have a Chromium-based browser around. I might eventually switch over to Epiphany for that.