126

cross-posted from: https://lemmy.crimedad.work/post/39255

Is self-hosted enough to avoid push notifications going through Apple and Google servers?

you are viewing a single comment's thread
view the rest of the comments
[-] plague_sapiens@lemmy.world 5 points 11 months ago* (last edited 11 months ago)

That's why everyone should use GrapheneOS. Sandboxed GooglePlay services can be used, if needed. I personally use 3 proprietary apps, one of them is WhatsApp Business (self-employed and for stupid dipshits that won't use anything else...), which is more privacy-friendly than the personal client itself. Join the resistance! Use GrapheneOS :)

Good read about push notifications on GOS: https://discuss.grapheneos.org/d/9407-this-is-why-i-use-grapheneos

[-] Rootiest@lemmy.world 11 points 11 months ago

Sandboxed GooglePlay services can be used, if needed.

I don't see how that would prevent this at all.

What is being discussed here is governments compromising the push notification service on Apple's servers (and presumably Google's as well)

Sandboxing Google services on your phone does nothing to change the fact that virtually all apps that receive messages/notifications are going to be using the push notification APIs that are compromised.

Whether or not private data is sent in those pushes and whether or not they are encrypted is up to the app developers.

It's common for push messages to simply be used as a triggering mechanism to tell the device to download the message securely so much of what is compromised in those cases will simply be done metadata or even just "a new message is available"

But even so, that information could be used to link your device to data they acquired using other methods based on the timing of the push and subsequent download or "pull"

The problem is that if you go ahead and disable push notifications/only use apps that allow you to, you are going to have abysmal battery life and an increase in data use because your phone will have to constantly ping cloud servers asking if new messages/notifications are available.

[-] plague_sapiens@lemmy.world 1 points 11 months ago* (last edited 11 months ago)

Yeah you're right. Sandboxed gplay services can still be used to surveil clients, good thing you can use another profile with gplay services and install apps (which needs those) on there, meaning no potential leaks for apps that use their own push notification service and closed APIs (Google or Firebase). Good thread about it: https://discuss.grapheneos.org/d/9407-this-is-why-i-use-grapheneos

[-] MigratingtoLemmy@lemmy.world 1 points 11 months ago

Would applications that don't use GMS be compromised too? Example: everything from F-droid

[-] Rootiest@lemmy.world 1 points 11 months ago

I think unless they use netfy or a similar alternative then yes.

The vast majority of apps will be using GCM or FCM for notifications.

Now whether or not those push messages are encrypted/don't contain private data is up to the app developer so how much is exposed can certainly vary.

[-] MigratingtoLemmy@lemmy.world 1 points 11 months ago* (last edited 11 months ago)

I get it. ~~Indeed, it's obvious now that even these apps would need to use Google's API~~ I stand corrected. Nope, apps from F-droid usually do not use GCM.

I hadn't heard of netfy before this, I'll have to take a look. I'm assuming that's an alternative FOSS framework for notifications? Can it be used as a drop-in replacement for most applications?

[-] Rootiest@lemmy.world 2 points 11 months ago

You're right, for some reason I thought Firebase was allowed.

Yeah netfy is a FOSS notification service.

As to drop-in replacements, I don't think such a thing really exists on the user side, this is fully up to the app developer in how they want to implement notifications.

To use netfy instead of FCM your app would need to be designed to do so or support it as an alternative option.

[-] navi@lemmy.tespia.org 7 points 11 months ago

How does it handle push notifications? If they come from googles push service then they'd be exploitable as well.

[-] waspentalive@lemmy.one 4 points 11 months ago

Indeed - it seems that this tracking is done completely outside of the phone, asking the network where, physically, the push notification was delivered (Tower, time, and date) to locate the phone and ostensibly the owner of the phone.

[-] possiblylinux127@lemmy.zip 5 points 11 months ago

What we need is more open hardware. Current phones are privacy issues because they are black boxes. Even if a libre device has bad security it always can be improved.

I use Lineage os on my phone with only free apps.

[-] plague_sapiens@lemmy.world 3 points 11 months ago

More open source hardware would be epic, but imo this trend will take years to grow if it even will succeed. Most people just don't care about their privacy at all and with hw and sw being open, there's less money to be earned because of easier plagiarism.

[-] steveman_ha@lemmy.world 2 points 11 months ago* (last edited 11 months ago)

Thats weird, it almost feels like a misalignment between our general needs for computing resource development, and the incentive structures produced by using capitalist economic markets to distribute even basic goods for survival...

[-] MigratingtoLemmy@lemmy.world 1 points 11 months ago

Put pressure to release the FP5 in the US. I don't know why they decided not to

[-] Ashyr@sh.itjust.works 1 points 11 months ago

How do you sandbox Google apps? Is it possible to do that with Google docs? I've been replacing everything else, but Google docs is difficult to replace.

[-] plague_sapiens@lemmy.world 2 points 11 months ago

Every app is sandboxed by default and has no permissions, which you can give them. Like StorageScope for accessing only certain files.

this post was submitted on 07 Dec 2023
126 points (97.0% liked)

Selfhosted

40246 readers
858 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS