• Dae@defcon.social
    link
    fedilink
    arrow-up
    0
    ·
    19 days ago

    @GrapheneOS then what is it if it’s not a partition? It does exist on the pixel 6a/bluejay, and you can flash pkmd.bin files to it. Whenever you do so, or do it incorrectly, etc, fastboot calls it a partition. I guess I must be missing a lot of information somewhere, but all the same, would love to see GrapheneOS develop further and be properly allowed to pass play integrity API.

    • GrapheneOS@grapheneos.socialOP
      link
      fedilink
      arrow-up
      0
      ·
      19 days ago

      @daedaevibin It’s not a partition. It gets flashed to the secure element via an API provided by the secure element. The fastboot firmware implemented support for flashing it via the image flashing interface. There’s also not actually a bootloader partition but rather those are containers with images nested inside. There a whole bunch of boot firmware images flashed to separate partitions from bootloader.img. An over-the-air update has them as separate images, not bundled into the bootloader.img.

      • GrapheneOS@grapheneos.socialOP
        link
        fedilink
        arrow-up
        1
        ·
        19 days ago

        @[email protected]

        > would love to see GrapheneOS develop further and be properly allowed to pass play integrity API.

        We fully preserve the privacy/security model and then substantially improve it. We use all of the same hardware-based security features as the stock Pixel OS but also a lot more including MTE (hardware memory tagging), PAC/BTI for userspace too, hardware-level disabling of new USB connections, USB data and the overall port for our USB-C port control feature and other features.

        • GrapheneOS@grapheneos.socialOP
          link
          fedilink
          arrow-up
          1
          ·
          19 days ago

          @[email protected]

          GrapheneOS fully supports hardware-based attestation. Google is entirely capable of verifying a device runs the genuine GrapheneOS releases:

          https://grapheneos.org/articles/attestation-compatibility-guide

          Play Integrity API has nothing to do with security regardless of how it’s marketed. It allows a device to pass if it hasn’t received security patches for 8 years. All it does is check if it’s a Google certified device and tries to stop spoofing within constraints of allowing highly insecure, ancient devices to pass.