Fuck Google with a stiff wire brush.

  • Arghblarg@lemmy.ca
    link
    fedilink
    arrow-up
    0
    ·
    15 days ago

    I read somewhere that GrapheneOS devs have a strategy which they believe will work – they strip out something or other about app/device attestation (?) from APK files before installing occurs, or the enforcement code itself from their spin of the OS, so sideloading (ie., user-controlled installation) can still work.

    I sure hope so… I think everyone in their respective country needs to scream at their local regulators about this.

    Of course, this will only help those whose devices GrapheneOS can run on.

      • rumba@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        14 days ago

        Shouldn’t they be keeping bypass strategies a secret right now?

        They’re up against a company with more money and developers than they know what to do with. This is, at most, a game of cat and mouse. Secrecy will buy them a sprint or so.

        If Google wants to go nuclear, they can do some rolling encryption bullshit or put a million calls all over the OS to check app validity and stop open source altogether.

    • Truscape@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      0
      ·
      15 days ago

      The GrapheneOS team is already in communications with an Android OEM to see if they can make a device that meets their specs, hopefully that bears fruit in a year or two.

    • other8026@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      15 days ago

      Google has already shared how apps’ developers will be verified. They’re adding another app that will have access to block installing apps or disable them. That won’t work on GrapheneOS because 1. the app won’t be installed and 2. the app won’t have that kind of privileged access.