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?
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.
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.
it’s also available from Mozilla’s repos and can be updated using Obtainium https://download.cdn.mozilla.net/pub/fenix/releases/
Cool.
But I’m not adding another method of updating apps just for the browser. F-Droid is where my non-play store apps live and update from, and I’d like to keep it that way.
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.
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?
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.
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.
The link(s) to add their F-Droid repo if not running DivestOS: https://divestos.org/pages/our_apps.html#repos
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?
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:
- https://github.com/mozilla-mobile/firefox-android
- https://github.com/mozilla-mobile/firefox-android/wiki#upcoming-migration-to-mozilla-central
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.
Quick update for anyone still reading this thread:
@fdroidorg@floss.social As with any other app, we flagged Fennec and Mull with KnownVuln until the app is updated. Contributors fixed the issues that delayed versions 130 and later. Stand by for the build.
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.
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.
Firefox 130 was released on the 3th of September, almost 2 months ago. This didn’t just happen in a short time frame.
