I remember reading an article where the government and Google were able to read notifications and record them from every android device. I wonder if Graphene might have patched this problem, and if not, do they have any plans to do so?

Thanks!

  • @[email protected]English
    30•3 months ago

    The issue lies with Google’s FCM (Firebase Cloud Messaging) system, so it’s not something GrapheneOS can really fix. As far as I know FCM doesn’t offer a way to encrypt notification content. Some apps like Signal work around this by instead of sending the message content, they send a little “wake up” notification. This tells Signal on your phone to wake up and it goes and retrieves the new message.

    If you don’t install Google Play Services, you won’t be impacted. But you’ll also not get notifications for most applications. There is an alternative push notification system called UnifiedPush which allows you to choose any server to handle your notifications (and even self host it). But it does require both the service and the app to support it, so it’s not very wide spread yet.

    • @[email protected]English
      10•3 months ago

      Lol, FCM sends the CONTENT of messages through Google?? Wtf why do we even have “E2EE” Whatsapp then?

      • @[email protected]English
        12•3 months ago

        I’ve never worked directly with FCM, but that’s my understanding of the issue. I don’t know about WhatsApp. But it may do the same thing as Signal where the notification is just a wake up call and then the app connects directly to the WhatsApp servers to get the actual message.

      • @[email protected]English
        6•3 months ago

        Firebase is a platform/service provided by Google, so it makes sense that the content goes thru Google’s servers.

        Also, E2EE in a closed-source app like WhatsApp, run by a nefarious corporation like Meta, was always a joke concept, a marketing ploy at best. People who are truly concerned about their privacy would never touch WhatsApp.

      • @GustavoFringEnglish
        6•3 months ago

        They are encrypted in transit but not E2EE unless the developer handles that themselves.

    • @[email protected]English
      2•3 months ago

      Why do we need a server to handle notifications anyway? Why isn’t it local to the device?

      • @[email protected]English
        4•3 months ago

        It’s mostly a power efficiency thing. Before push notifications were the norm, most apps used a polling method. They had the application send a request every X seconds asking “anything new”. There wasn’t coordination between apps, so even every app checked once every 30s, it likely wouldn’t be on the same 30s. This caused the device to wake up a lot and never let it switch into low power mode.

        A push notifications system like FCM or UnifiedPush means only a single application needs to run in the background. It maintains a persistent connection to the push notification service and waits for a message. When it receives one it wakes up the relevant app and passes it the details.

    • @MigratingtoLemmy
      OPEnglish
      1•3 months ago

      If I were to install MicroG in a different profile would the rest of my push notifications be compromised too?

        • @MigratingtoLemmy
          OPEnglish
          1•3 months ago

          Essentially, the apps which don’t use Google FCM service are not affected (from what I understand?). I assume that there isn’t a problem on the client-side and this exploit works purely because Google stores these notifications.

            • @MigratingtoLemmy
              OPEnglish
              1•3 months ago

              Would you happen to know what WhatsApp and Signal use? I believe FOSS apps from F-droid do not use Google’s notification service

                • @MigratingtoLemmy
                  OPEnglish
                  1•3 months ago

                  Thanks, I’ll go read some more. I’m trying to move away from WhatsApp and wanted to run Signal in my main profile on Graphene. I hope I can use it without FCM there.

          • @[email protected]English
            1•3 months ago

            Anything using FCM will be effected. UnifiedPush which I mentioned I don’t believe has an option to encrypt notification content either. Using it you’d already at least have the option of using a provider with a better privacy policy or self hosting it.

            • @[email protected]English
              2•3 months ago

              I don’t believe has an option to encrypt notification content either.

              This is not an option you would actually want from any service.

              You don’t want to be giving the plain text message to anyone to encrypt. Instead the notification contents should be given to the service provider (FCM or anyone else) already encrypted and only able to be decrypted by the app.

  • /bin/bash/English
    5•3 months ago

    I don’t recall any article like you said; can you provide me with a link?

    Also, reading notifications is only possible if the notifications are not encrypted; otherwise, it is not possible.

    And this relies on the service that is sending the notification and has nothing to do with the OS you are using.