Check your proton VPN app, and look for the netshield setting. If it’s enabled, you are using VPN based ad blockers, but if it’s not enabled, you should turn it on.
circuscritic
- 0 Posts
- 49 Comments
Joined 1 year ago
Cake day: June 12th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
Regardless, most of those VPN-based ad blockers are just using their own flavor and combination of block lists. I’m sure some get a little fancier, but that’s gist of it. Which is something, that ProtonVPN also offers I think they call it netshield or something like that.
The paid brave VPN service? If so, I can’t speak to it because I have never used it, but I assume it functions much like a normal VPN provider where they’re running their own ad block lists on the exit node, but I have no idea what those lists are or their effectiveness. And yes, that would prevent your from concurrently running another systemwide VPN tunnel.
Firefox with uBo is good and not trying to convince you to abandon Firefox on Android, certainly not for your desktop OS.
The issue that thought is OP is referring to is about security, and while privacy and security aren’t mutually exclusive, sometimes you trade off one for the other.
Personally, I prefer Chromium forks because I already take other privacy measures that I’m content with, and I would prefer the security advantages those browsers provide on Android.
But sometimes, if there’s a website that I trust is not malicious, but there is an extension I prefer to view it with, I use Mull or Ice Raven. Both being Firefox on android forks, the former being a security/privacy hardened variant.
I want to reiterate, that this is only in regards to Android browsers and I’m definitely not saying to install Google Chrome, or even Google’s own Chromium. I’m talking about hardened forks of their open source chromium project, such as Mulch and Cromite.
You’re talking about ad blockers that leverage a VPN connection, but Cromite is a hardened Chromium fork with built in ad blocking, including adding custom lists.
Other Chromium forks, including Mulch, also support browser level custom DNS configs.
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.
Extensions are another vector. But putting that aside, because I agree ads are a much larger threat:
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.
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.
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.
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.
No one is saying use Google’s version of Chromium. There are hardened forks available, such as Mulch and Cromite.
It means that one malicious site can compromise your entire phone.
See the replies below regarding per-site process isolation.
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:
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.
Source: The developer of Mull, Mulch, & DivestOS
663·1 month agoProjectivy launcher, problem
solvedadequately duct taped.Stop connecting your TVs directly to the internet, I don’t care what OS it’s running. The trend is clear with TV manufacturers, and if your current TV OS doesn’t yet inject ads into your streaming box’s HDMI stream, why risk it updating? Because that’s coming soon enough, and I imagine what it does, an update requiring your TV to have internet connection won’t be far behind.
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
11·1 month agoNot everyone has a safety deposit box, or the ability to access a proper and secure off-site storage.
And if you’re just keeping those in your house, then fire, flood, and other incidents can destroy all copies at once.
Nah, I’m with you, except I use BitWarden.
There are somethings either worth paying someone else to host, or where you trust a 3rd party more than you’re own setup. I realize other users may feel different, but ultimately it’s a judgement call
BW has been a pretty great opensource company, and it’s worth my $10/yr for premium.
You should enable it anyways. A lot apps, especially from big companies like banks, use DNS based telemetry and tracking services. Many of which will then be blocked by netshield, if it’s enabled.