To me, it’s gotta be the microphone

  • The 8232 Project@lemmy.ml
    link
    fedilink
    arrow-up
    17
    ·
    edit-2
    18 days ago

    This depends on what you’re trying to defend against. In my opinion (on GrapheneOS):

    • “Accessibility” permission (i.e. full control of the device)
    • “Network” permission
    • “Modify system settings” permission
    • “Install unknown apps” permission
    • Any permission that allows apps to communicate with one another (such as a reduced sandbox, file permission, or app communication scopes)

    Those are the only permissions that I can think of off the top of my head that could potentially allow an app to phone home. Turning off Wi-Fi for the device does little if the app also has the “Wi-Fi control” permission.

    • Quail4789@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      18 days ago

      App communication scopes isn’t the scary thing, it’s the solution. Standard Android sandbox allows apps to communicate if they mutually agree to it. Scopes will allow you to limit that.

      • The 8232 Project@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        17 days ago

        I know, but since we’re referring to permissions here, I wanted to refer to each of them by the permission names.