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.
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
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
See the replies below regarding per-site process isolation.
It means that one malicious site can compromise your entire phone.
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.
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.
It's like you're arguing because you like to argue, and can't admit that you're wrong. So you keep finding new ways to qualify your response in the hopes that I forget what this is even about.
Chromium is significantly more secure than Firefox Gecko on Android. That is according to the developers of probably the two most well regarded hardened Android ROMs.
One of which, Graphene, even advises completely avoiding Gecko based browsers.
Which is what I said in my original comment, well, the part about relative security.
You've also claimed that at most, a malicious android application can only harm battery life and cause network issues, which is objectively false. I'm honestly kind of confused why you even said that, but whatever.
I never said no one should use Firefox based browsers on Android, I just said they weren't as secure and that user should understand the risks associated with them.
But what I'm most confused and perplexed by, is your insistence that only high risk individuals should be concerned with using a browser that comes with, at minimum, double the attack service they're exposed to when browsing the web.
Again, that is per the GrapheneOS wiki/FAQ.
I mean, we're not talking about some hardcore and incredibly inconvenient levels of unnecessary OPSEC for the sake of OPSEC, we're talking about a browser.
Tell you what, if you post a link to your GitHub showing me the hardened Android ROM that you develop, or heavily contribute to, I would be happy to revise my opinion on your credibility versus those developers.
What if I told you I work in information security, and your not impressing me, or tripping me up, by using terms like defense in depth and attack chains, nor am I confused and unable see through your misrepresenting Graphene's threat model to imply it only matters for high threat risk individuals.
Just because I said I don't have enough low level understanding of Android development to refute those devs write-ups on Android browser security, doesn't mean I'm coming here without a professionally informed understanding of security, and all the terms you keep throwing out to muddy the issue.
So, I'll leave it there. I will take my professional knowledge and experiences, along with my judgment on which sources I incorporate into my broader understanding of this situation, and agree to disagree with your analysis and conclusions.
https://wiki.mozilla.org/Project_Fission
It's because you are making extreme claims without any sources.
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
what divestOS is actually saying:
https://divestos.org/pages/browsers
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
You're wrong
Source: same as yours. My butt.
Source: The developer of Mull, Mulch, & DivestOS
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.
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.
Extensions are another vector. But putting that aside, because I agree ads are a much larger threat:
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.