Android
DROID DOES
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:
Rules
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:
view the rest of the comments
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.