Google tries to defend its Web Environment Integrity - eviltoast
Google Tries to Defend Its Web Environment Integrity as Critics Slam It as Dangerous
techreport.com
Google has defended its Web Environment Integrity on the grounds that it aims to make web browsing more private and safe through tokens.

I’m happy to see this being noticed more and more. Google wants to destroy the open web, so it’s a lot at stake.

Google basically says “Trust us”. What a joke.

  • Zak@lemmy.worldEnglish
    23·
    1 year ago

    I used a rooted phone without Google apps on it and so many apps simply refused to work. They use Googles api in the background

    This has nothing to do with being rooted but with Google encouraging people to build apps using its proprietary libraries to make Google Android more valuable than Android Open Source Project. There may be a connection to the EU’s attempts to stop Google from forcibly bundling several of its other apps with the Play Store.

    For most use cases, good alternatives are available and it’s just a matter of developers being lazy, but I’m not sure there’s another good option for chat apps to get timely notifications without high battery consumption. MicroG provides an open source alternative to Google’s libraries and works for most apps, including chat notifications.

    • Max-P@lemmy.max-p.meEnglish
      6·
      1 year ago

      It’s a bit worse than just Google libraries, apps can use Play Integrity which uses hardware attestation to validate it’s bootloader lock status and that it’s running a vendor signed and Google approved ROM.

      Current bypasses emulate older devices without the necessary hardware, but those will eventually stop working and there won’t be bypasses unless someone leaks some master keys or finds TPM exploits to trick it into signing the integrity request. It’s very bad.

      • Zak@lemmy.worldEnglish
        3·
        1 year ago

        Yes, but they’re two separate issues. Many apps that don’t care whether you have root or a third-party Android build use Google’s libraries.

        Patching apps is another workaround. It won’t beat server-side checks, but I think those are still fairly rare. ReVanced makes it easy to do, though I’m not sure there are patches related to SafetyNet yet.