GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 09:54:02 JST GrapheneOS GrapheneOS

    A growing number of apps are using the Play Integrity API to enforce installation from the Play Store. This is clearly highly illegal anti-competitive behavior. It doesn't impact GrapheneOS users installing apps with the sandboxed Play Store but does impact other install sources.

    In conversation about 9 days ago from grapheneos.social permalink
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:41 JST GrapheneOS GrapheneOS
      in reply to

      If you run into apps banning using GrapheneOS with Play Integrity, make a Play Store review with no links asking to stop banning a more secure OS. Next, make a customer support request linking https://grapheneos.org/articles/attestation-compatibility-guide. Multiple apps have permitted GrapheneOS due to these efforts.

      In conversation about 9 days ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: grapheneos.org
        GrapheneOS attestation compatibility guide
        from @GrapheneOS
        Guide on using remote attestation in a way that's compatible with GrapheneOS.
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:42 JST GrapheneOS GrapheneOS
      in reply to

      Multiple prominent banking apps in Europe have already implemented support for GrapheneOS via hardware attestation. The pace of apps adopting the Play Integrity API is unfortunately currently faster than apps adding support for GrapheneOS. This is due to Google marketing it.

      In conversation about 9 days ago permalink
      Rich Felker repeated this.
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:43 JST GrapheneOS GrapheneOS
      in reply to

      Even if apps insist on doing these kinds of integrity checks, they can still permit GrapheneOS. We provide a guide on verifying GrapheneOS via hardware attestation at https://grapheneos.org/articles/attestation-compatibility-guide. They can still fall back to Play Integrity API for insecure devices without this.

      In conversation about 9 days ago permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: grapheneos.org
        GrapheneOS attestation compatibility guide
        from @GrapheneOS
        Guide on using remote attestation in a way that's compatible with GrapheneOS.
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:44 JST GrapheneOS GrapheneOS
      in reply to

      There's no security value to enforcing using devices licensing Google Mobile Services. The vast majority of those devices are highly insecure. Software-based attestation (device integrity) is also highly insecure and easy for attackers to bypass. This is only hurting competition.

      In conversation about 9 days ago permalink
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:44 JST GrapheneOS GrapheneOS
      in reply to

      Hardware-based attestation can be secure, but the way the Play Integrity API uses it is also highly insecure. It can be bypassed via leaked keys from the most insecure Android devices in the ecosystem. Secure way to use it is pinning, not trusting everything chaining to a root.

      In conversation about 9 days ago permalink
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:45 JST GrapheneOS GrapheneOS
      in reply to

      Google Play Integrity permits highly insecure devices with years of missing High/Critical severity security patches. They pretend any device licensing Google Mobile Services is secure while running the stock OS and anything else is insecure. This is a lie to lock out competition.

      In conversation about 9 days ago permalink
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:46 JST GrapheneOS GrapheneOS
      in reply to

      Google's Play Integrity API is quite different and only supports verifying devices licensing Google Mobile Devices with the stock OS. It has support for enforcing installing apps from the Play Store. None of this has anything to do with security. It's purely anti-competitive.

      In conversation about 9 days ago permalink
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:47 JST GrapheneOS GrapheneOS
      in reply to

      It's worth noting Android has a standard hardware attestation API for verifying the hardware, firmware, OS and app. This supports alternate roots of trust and non-stock operating systems if apps choose to support it. Apps could perform stronger checks while allowing GrapheneOS.

      In conversation about 9 days ago permalink
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:47 JST GrapheneOS GrapheneOS
      in reply to

      Android's hardware attestation API has anti-competition issues due to the official verification libraries hard-wiring the Google roots and encouraging only permitting the stock OS. However, it does fully support any other OS with verified boot and can be used with other root CAs.

      In conversation about 9 days ago permalink
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:48 JST GrapheneOS GrapheneOS
      in reply to

      We're going to add a secure way of working around this without breaking the app source security model. We'll be adding support for having the OS automatically verify the Play Store signing metadata and then inform Play services those apps were installed from the Play Store.

      In conversation about 9 days ago permalink
    • Embed this notice
      GrapheneOS (grapheneos@grapheneos.social)'s status on Friday, 23-May-2025 11:05:49 JST GrapheneOS GrapheneOS
      in reply to

      This is being done alongside Google recommending app developers forbid installing their apps from the Play Store on operating systems not licensing Google Mobile Services. The combination of these feature ends up blocking users from easily using the apps without modifying them.

      In conversation about 9 days ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.