If, like me, you’ve relied on Fennec as a more tolerable version of Firefox for Android, you may have gotten some bad news in the latest F-droid update cycle.

Fennec has fallen so far behind on updates that serious security patches implemented by Mozilla in Firefox haven’t been applied to the fork, and Fennec is therefore still breachable.

The developer responded two weeks ago that they were “short on time”, and there still isn’t a new, secure version available. This appears to be due to that recurring weak link in open source development: small teams, confronted by real life demands like time and money?

  • ColdWater@lemmy.caEnglish
    6·
    2 days ago

    If you want an up-to-date and lightweight Firefox fork, try Waterfox that’s what I’m using right now

    • Handles@leminal.space
      OPEnglish
      3·
      1 day ago

      Cool cool, glad to see I may have jumped the gun. But I had cause to try a couple other Firefoxes (Nightly Beta and Mull) in the meantime!

      Now I’ll just be refreshing F-Droid every five minutes until the update comes through 😄

  • hypertown@lemmy.worldEnglish
    96·
    2 days ago

    It’s just very unfortunate timing. Google removed some library Firefox depended on in NDK and it meant developers need to make significant changes to their packaging system. At the same time critical vulnerably was discovered in Firefox. On top of that, everything happened when main developer of Fennec was away from home and short on time. But from what I’ve seen on Fennec gitlab most of the work is done so you should expect update soon.

    • doctortran@lemm.eeEnglish
      28·
      2 days ago

      Yep, it’s this. Annoying change, but from what I was reading, perfectly solvable with a little time. Unfortunately the dev was moving house, so they fell a version behind at the worst possible moment, but they’re aware of the issue. I’m not too concerned.

      Had it not been for FDroid’s warning, I wouldn’t have even realized Fennec was a version behind (now 2). Normally it’s not that big a deal.

    • Nonononoki@lemmy.worldEnglish
      148·
      2 days ago

      Firefox 130 was released on the 3th of September, almost 2 months ago. This didn’t just happen in a short time frame.

      • doctortran@lemm.eeEnglish
        91·
        2 days ago

        Fennec being a version behind for over a month because the dev was absent wouldn’t normally be that big a deal if not for the vulnerability being discovered.

  • scsi@lemm.eeEnglish
    41·
    2 days ago

    A bit of backstory on how we got here - in June 2024 Mozilla chose to (a) integrate the source tree of Firefox Mobile into their huge monorepo (“gecko-dev”), and (b) move the source off of Github onto their own git servers (“Mozilla Central”). You can read about it in the now-archived old repo:

    This was then compounded by a core Android build kit (“NDK”) choosing to remove parts of the toolchain which is/was used to build Firefox releases (ergo, forcing another change to build process):

    Together these have caused a bit of a kerfuffle in getting new releases compiled and released via the official F-Droid methodology. See the other comment about the Mull version in their private repo, they’re having to use a Mozilla pre-built clang (a compiler toolchain) now to make it work for the time being.

  • brsrklf@jlai.luEnglish
    492·
    3 days ago

    What do you find not tolerable in standard Firefox and what did this browser do that made it better?

    I know firefox is rather memory heavy, but despite that it’s still my go-to browser, both for desktop and mobile.

    • AnyOldName3@lemmy.worldEnglish
      391·
      3 days ago

      Upstream Firefox doesn’t comply with FDroid’s rules (thanks to the ‘proprietary bits and telemetry’ Handles mentioned), so is only available from the Play Store or as a loose APK that won’t auto-update.

    • Handles@leminal.space
      OPEnglish
      181·
      3 days ago

      I think this is beside the point here, but as it says in the F-droid description, their build “has proprietary bits and telemetry removed”.

  • s08nlql9@lemm.eeEnglish
    5·
    1 day ago

    For those who want to install standard FF via Obtainium use this:

    https://download.cdn.mozilla.net/pub/fenix/releases/

    Then add intermediate links (EDIT: this will only fetch releases like 130.0 or 130.1, etc. so feel free to edit regex if you want to match other versions like 130.0.1)

    [0-9]+\.[0-9]+/$

android/$

fenix-[0-9]+\.[0-9]+-android-arm64-v8a/$

    EDIT: based on https://github.com/ImranR98/Obtainium/issues/1625#issuecomment-2120736614

  • gaylord_fartmaster@lemmy.worldEnglish
    25·
    3 days ago

    I’ll just throw out Mull from DivestOS’s third-party f-droid repo as an up to date alternative. The newest versions are incompatible with the main repo but here is their explanation:

    Updated Mull to 131.0.0, has 14+1+25 security fixes from the previous 129.0.2 release. In order to resolve the compilation issue introduced in 130, Mull is now compiled using Mozilla’s prebuilt clang toolchain. This however is incompatible with the F-Droid.org inclusion criteria, so these updates (for now at least) will only be available via the DivestOS.org F-Droid repository. Please note, while this adds a prebuilt dependency, the result does still remain FOSS.

    • Handles@leminal.space
      OPEnglish
      8·
      3 days ago

      Ah yes, the toolchain changes appear to be a stumbling stone for the Fennec devs as well. That kind of thing doesn’t exactly speed up new releases, I’m sure.

      What are your experiences with Mull? Is it generally compatible with Firefox plugins, and are there performance improvements as well as in security?

      • iturnedintoanewt@lemm.eeEnglish
        6·
        2 days ago

        IMHO as i have it as my daily browser, it can become troublesome with booking websites (flights, tickets, hotels, restaurant orders, shopping). They don’t like whatever Mull blocks, and at some point during any booking process you’ll be unable to complete it. Sometimes during the payment step, so it can be… Frustrating.

        • Handles@leminal.space
          OPEnglish
          3·
          2 days ago

          I experience similar, if rarely, with my about:config modifications and muBlock add-on [edit: that was on Fennec, I expect similar on other Fenix forks]. Those things I blame more on the modern web than on any browser :/

      • airglow@lemmy.worldEnglish
        5·
        2 days ago

        Mull has defaults that improve privacy at the cost of performance and website compatibility. They maintain a list of changes that you can reverse through about:config. If Mull seems slow for you, consider re-enabling the JavaScript JIT.

      • gaylord_fartmaster@lemmy.worldEnglish
        5·
        2 days ago

        I’ve been using it as my primary browser on Android for years so I don’t really have much to compare it to, but I haven’t had any issues with extension compatibility. It includes changes from Tor browser and Arkenfox so it’s more privacy-focused than on performance.

    • doctortran@lemm.eeEnglish
      5·
      2 days ago

      The only reason the Fennec devs haven’t announced this is that they’ve been moving but they’re basically working on the same things to get it back on F Droid.

  • jaaaardvark@lemm.eeEnglish
    4·
    2 days ago

    Is there a way to transfer my browser profile on Android between Fennec and Firefox?

    • doctortran@lemm.eeEnglish
      5·
      2 days ago

      Honestly, just wait a little bit, both Fennec and Mull will get it sorted soon and you’ll see an update. If the vulnerability is worrying you that much, I’d honestly just download the standard Firefox APK for the time being and use it while waiting on Mull to update on fdroid. It likely won’t be more than a couple days.

    • Teknikal@eviltoast.orgEnglish
      2·
      2 days ago

      I used the Mozilla account sync thing that’s built in but it didn’t restore the extensions.

      bookmarks and passwords seem to have copied over to the DivestOS one though.

  • hendrik@palaver.p3x.deEnglish
    3·
    2 days ago

    I got the same warning for Mull. Is the patching so extensive? I always thought they have a patchset for some of the shortcomings and just apply that onto the newest Firefox version… Or do they do a full code review on all of the changes?

    • TeddE@lemmy.worldEnglish
      101·
      2 days ago

      I could be mistaken, but since it’s a Mozilla base code and F-Droid distribution chain, I’m not sure where Google can stick it’s thumb in the pie.

      • finitebanjo@lemmy.worldEnglish
        2·
        1 day ago

        Mozilla relied on an Android NDK to build correctly, became no longer available right as a firefox vulnerability came out and the Fennec dev was away from home.