LibreWolf is a great privacy oriented Browser for desktop. But there is no version for android or IOS . There are some like mull but they have their own problems. Mobile phones stay with us most of the day. So we need extra privacy for it.

  • circuscritic@lemmy.caEnglish
    3816·
    2 months ago

    This always gets downvoted, because it’s a painful truth, but Chromium on Android is significantly more secure than Firefox.

    There is a reason why the default included browser on GrapheneOS, Vanadium, is a Chromium fork.

    So I’m sorry, until Firefox on Android catches up to Chromium, another Firefox fork isn’t going to make the impact on the ecosystem that you think it is.

    I’m not saying you can’t or shouldn’t use Firefox forks on Android, I’m saying do so being aware of their limitations relative to Chromium forks, such as Cromite, or Mulch, the latter being the same dev as Mull. That same dev also has a lengthy write-up going over the technical details of why Chromium is more secure than Firefox on Android.

    This has nothing to do with desktop browser engines, this is specifically and exclusively in regards to Android browsers

              • circuscritic@lemmy.caEnglish
                51·
                2 months ago

                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.

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

                That sounds like the exposed attack surface is a lot more than just whatever sites are running under your Firefox process.

                But what do I know, I’m not a developer of security-hardened Android forks, so I just have to pick which randos on the internet I choose to believe. When the developers of DivestOS and GrapheneOS both have lengthy write-ups on why chromium base browsers are significantly more secure, I’m going to believe them because I don’t have the low level technical knowledge to refute what they’re saying.

                  • circuscritic@lemmy.caEnglish
                    4·
                    2 months ago

                    Right, so if Gecko based browsers can cause that kind of security concern on Graphene, what does that mean for people using Android ROMs that are not hardened, or, OEM variants that do not receive regular security updates?

                    Any app installed by a user that takes advantage of an active and unpatched CVE, can do all sorts of actions to compromise an entire phone, or critical parts of it. Are you saying that’s not the case?

                    The difference between a compromised app, and a browser, is that even a “safe” Firefox install is used to browse a near infinite possibility of websites, any number of which might be running an active campaign targeting unpatched Android vulnerabilities.

                    It sounds like you’re saying that despite Firefox Geckos significantly larger attack surface, the fact that Chromium doesn’t eliminate all risk, means there’s no difference.

    • helpmyusernamewontfi@lemmy.today
      English
      1·
      2 months ago

      it really sucks tho, because most chromium forks still force you to use a google account in order to sync, and thats if they don’t strip google entirely. there’s brave, but I haven’t had the best of experiences with that browser.

      I can still self host something like floccus to “sync” bookmarks, and use kde connect to send browser tabs from one device to another, but I still wish it was as convenient as firefox; which iirc, let’s you self host their sync service

      • circuscritic@lemmy.caEnglish
        71·
        2 months ago

        Pretty sure I told you where you could find more information, as well as pointing out that the default browser on Graphene is a hardened Chromium browser, not Firefox Gecko.

        But okay, here, I can even do that little bit of searching for you:

        https://divestos.org/pages/browsers

      • circuscritic@lemmy.caEnglish
        8·
        2 months ago

        What is per-site process isolation?

        Per-site process isolation is a powerful security feature that seeks to limit exposure of a malicious website/script abusing a security vulnerability. Firefox calls per-site process isolation Fission and is enabled by default on desktop. Fission is not yet enabled by default on Android, and when manually enabled it results in a severely degraded/broken experience. Furthermore Firefox on Android does not take advantage of Android’s isolatedProcess flag for completely confining application services. Standalone Chromium based browsers strictly isolate websites to their own process.

        https://divestos.org/pages/browsers

        Source: The developer of Mull, Mulch, & DivestOS

        • teuto@lemmy.teuto.icuEnglish
          6·
          2 months ago

          Personally I would argue that allowing users to install extensions, mostly adblockers, you remove what’s probably the single most common real world vector for attackers, ads. So while chromium browsers may be more secure I would say you’re probably less likely to run into a problem with a firefox based browser with ublock origin on it, mobile or desktop.

          • circuscritic@lemmy.caEnglish
            1·
            2 months ago

            Extensions are another vector. But putting that aside, because I agree ads are a much larger threat:

            https://github.com/uazo/cromite

            Cromite a Bromite fork with ad blocking and privacy enhancements; take back your browser!

            Also, Mulch lets you pick your DNS provider. So even if you don’t already have system, or network, wide ad blocking, it’s not like you’re deluged in ads.

            Again, I’m not saying no one should use Gecko based browsers, I’m just repeating what developers of respected hardened security ROMs have written about. Actually, that’s not true, I’m taking a softer approach as the GrapheneOS wiki/FAQ says NOT to use Gecko based browsers.

        • GHiLA@sh.itjust.worksEnglish
          5·
          2 months ago

          Corrected. Firefox is less secure than Chromium-based browsers.

          And if you had that in your butt the whole time, you should’ve gotten it out earlier.