• 0 Posts
  • 32 Comments
Joined 6 months ago
cake
Cake day: June 6th, 2025

help-circle










  • Yes absolutely. In fact, you’ve touched on the very issue that people don’t understand with Google - the likelihood of the risk.

    Most people think that because the consequence of Google getting your data is low, it’s a lesser risk than a hacker getting into your device (very high consequence). But likelihood is just as important with risk. It’s very unlikely a competent hacker will attack your device (moreso with good practice on your part), so the risk is still low even though the severity is high. But it is an absolute certainty that Google will get your data - so even though the severity is low the risk is still significant, and arguably Google present a more significant risk than a hacker.

    I’m not advocating using Google over F-Droid, or that Google’s change here is good, or even lawful. This is a textbook anti-trust type case that the EU prosecuted against in the past. However, unfortunately governments seem gung-ho for this to happen this time around.

    All I’m saying is that if F-Droid want to tout the security of their service, they probably shouldn’t leave the door open for attackers to use their app as a vector for attacking devices. Their response to this wasn’t strong enough to justify their implied claim that they are at the forefront of security. They’re much better than Google, sure, but they should be trying harder if they want to lead.


  • Why do you think vulnerabilities and functionality are mutually exclusive??

    Of course being able to connect to other repos is a useful function of F-Droid, I use it for several. However, functionality also opens up potential doors for attackers.

    The most effective way to secure your device is to limit functionality. Then, it becomes a trade off between what functionality you want or can do without, and what potential risk you’re willing to accept.

    It’s easy to ignore risk and enable all functionality, and sometimes that’s nice to do, but you’ve got to find a balance.

    My point here is that F-Droid is arguing about their viability because of their security, while running a service that has a known vulnerability.


  • F-Droid is in a bit of a bad position to argue here, as it does have a genuine security vulnerability that many choose to avoid the service for. Basically, while they say “our store is safe and contains zero malware” this isn’t necessarily true of the 3rd party repositories you can subscribe to with their app. So, if an attacker compromises the F-Droid app on your device, they can subscribe to their own repository and load malicious apps onto your device through the F-Droid app.

    Unfortunately this move by Google is a bit of a death knell anyway. I can’t see governments preventing Google from doing this, particularly not now they’ve established means of access (paying) for data Google holds, and especially since governments (eg UK) are now mandating you install government apps on your phone.