AOSP with MicroG vs Nextdns with good lists (lemmy.ml)
from abcd@cuddly.space to privacy@lemmy.ml on 31 Aug 08:52
https://cuddly.space/users/abcd/statuses/113055313002488016

AOSP with MicroG vs Nextdns with good lists

How better is AOSP or Graphene OS with MicroG or Sandboxed google services compared to just using NextDNS with some good filters.
I mean microg or graphene os will still connect to internet for google stuff I use. Also I can block internet access for a domain using NextDNS which is quite similiar to cutting network access in graphene OS. So how come stock android with NextDNS is less private than MicroG/GrapheneOS.
@privacy

#privacy

threaded - newest

jet@hackertalks.com on 31 Aug 09:07 next collapse

www.privacyguides.org/en/os/android-overview/#cho…

www.privacyguides.org/en/android/distributions/

share.privacyguides.org/tools/grapheneos/

There you go. Everything you wanted to know and more about Android security and trade-offs

SleepyWheel@sh.itjust.works on 31 Aug 12:25 collapse

I use GrapheneOS and NextDNS. And NoScript. There’s some overkill there but I figure why not.

To your question, GrapheneOS has put a lot of thought into features like sandboxing Google Play services so you can choose to use none/some/all depending on your preference. I would think that’s probably a smoother experience than trying to block google services selectively via NextDNS. GrapeheneOS also makes it easier to manage per-app permissions and security features.

abcd@cuddly.space on 02 Sep 03:28 collapse

@SleepyWheel Besides smoother are there any technical advantage?

SleepyWheel@sh.itjust.works on 04 Sep 12:56 collapse

Honestly I’m not technically knowledgeable enough to answer, you can have a read of their FAQs. But my understanding is that the sandbox allows some google services to be used, but without privileged access to the rest of the system. As opposed to blocking them entirely, which would mean you couldn’t use those services at all. grapheneos.org/usage#sandboxed-google-play