• 0 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle






  • I have used FF based browsers for a long time and still do. I recently saw this from the GrapheneOS developers, which kinda freaks me out and has me considering switching to a Chromium based browser:

    https://grapheneos.org/usage#web-browsing

    Chromium-based browsers like Vanadium provide the strongest sandbox implementation, leagues ahead of the alternatives. It is much harder to escape from the sandbox and it provides much more than acting as a barrier to compromising the rest of the OS. Site isolation enforces security boundaries around each site using the sandbox by placing each site into an isolated sandbox… Browsers without site isolation are very vulnerable to attacks like Spectre…

    Avoid Gecko-based browsers like Firefox as they’re currently much more vulnerable to exploitation and inherently add a huge amount of attack surface. Gecko doesn’t have a WebView implementation (GeckoView is not a WebView implementation), so it has to be used alongside the Chromium-based WebView rather than instead of Chromium, which means having the remote attack surface of two separate browser engines instead of only one. Firefox / Gecko also bypass or cripple a fair bit of the upstream and GrapheneOS hardening work for apps. Worst of all, Firefox does not have internal sandboxing on Android. This is despite the fact that Chromium semantic sandbox layer on Android is implemented via the OS isolatedProcess feature, which is a very easy to use boolean property for app service processes to provide strong isolation with only the ability to communicate with the app running them via the standard service API. Even in the desktop version, Firefox’s sandbox is still substantially weaker (especially on Linux) and lacks full support for isolating sites from each other rather than only containing content as a whole. The sandbox has been gradually improving on the desktop but it isn’t happening for their Android browser yet.

    EDIT: I really hope Ladybird turns out to be amazing.







  • Eternal Strands. I’m loving it! I almost quit playing a few times in the first couple of hours but once you get into the loop of it and learn some more skills and combat techniques, things get amazing.

    It has that same sense of wonder and exploration that I got from BOTW, even though it’s broken up into zones instead of one open world. It also takes a lot of great parts from Dragon’s Dogma, Shadow of the Colossus, and Monster Hunter, while still very much being its own thing. Plus, the loot is not overwhelming and feels meaningful, and you can re-spec all gear without penalty.

    It’s all really streamlined to maximize fun.




  • oaklandnative@lemmy.worldtoLinux@lemmy.ml"SO proof" distro
    link
    fedilink
    arrow-up
    10
    ·
    edit-2
    7 months ago

    I vote the same, but I’d suggest a uBlue spin of the Fedora Atomic desktops. They have better defaults (all batteries included, as they say) and are easier to use overall IMHO. Bluefin and Bazzite are both great options, and both offer KDE and Gnome variants.

    https://universal-blue.org/

    Edit: TIL the KDE version of Bluefin is called Aurora.

    BTW, uBlue is getting some big recognition lately. They have been on the Fedora Podcast (official) and Framework Laptops has official instructions on their website for installing Bluefin and Bazzite.



  • I added this edit above. Pasting here in case you are curious. Cheers.

    EDIT: This thread motivated me to try and fix this issue. Installing Firefox using rpm-ostree worked. I expected it would, though I am still hoping to figure this out using the Flatpak version at some point. I also tried using Distrobox/Box Buddy to create a Fedora 40 box and install Firefox there. That version of Firefox couldn’t even see my NAS at all (unlike the Flatpak which could see my NAS but couldn’t upload files from the NAS to Proton). This was my first time ever using Distrobox. I thought it was super cool to see it in action and get a working Firefox, even though I couldn’t use it to access my NAS as hoped.



  • Thanks. I tried that using:

    smb://[NAS NAME].local/[FOLDER NAME]/

    I copied that path straight out of the Files app. Unfortunately it does not work. There is a yellow exclamation point flag next to it that says “This is not a valid option.”

    I ended up installing the rpm-ostree version of Firefox, which accesses my Nas just fine for proton drive uploads. I do hope to eventually figure out how to do this with flatpak/flatseal, but this works for now at least. I appreciate the help!