Comment on This New Android Smartphone Is For Everyone Who Misses the Blackberry

• bdonvr@thelemmy.club ⁨3⁩ ⁨weeks⁩ ago

  Unfortunately the GrapheneOS team said it doesn’t meet their requirements. Their requirements are suuuuuuper specific which is why it’s only on Pixel devices.

  They have said that the bootloader can be unlocked, so some sort of ROM support is possible.

  GrapheneOS complete requirements:

  • Support for using alternate operating systems including full hardware security functionality
  • Complete monthly Android Security Bulletin patches without any regular delays longer than a week for device support code (firmware, drivers and HALs)
  • At least 5 years of updates from launch for device support code with phones (Pixels now have 7) and 7 years with tablets
  • Device support code updated to new monthly, quarterly and yearly releases of AOSP within several months to provide new security improvements (Pixels receive these in the month they’re released)
  • Linux 6.1, 6.6 or 6.12 Generic Kernel Image (GKI) support
  • Hardware accelerated virtualization usable by GrapheneOS (ideally pKVM to match Pixels but another usable implementation may be acceptable)
  • Hardware memory tagging (ARM MTE or equivalent)
  • Hardware-based coarse grained Control Flow Integrity (CFI) for baseline coverage where type-based CFI isn’t used or can’t be deployed (BTI/PAC, CET IBT or equivalent)
  • PXN, SMEP or equivalent
  • PAN, SMAP or equivalent
  • Isolated radios (cellular, Wi-Fi, Bluetooth, NFC, etc.), GPU, SSD, media encode / decode, image processor and other components
  • Support for A/B updates of both the firmware and OS images with automatic rollback if the initial boot fails one or more times
  • Verified boot with rollback protection for firmware
  • Verified boot with rollback protection for the OS (Android Verified Boot)
  • Verified boot key fingerprint for yellow boot state displayed with a secure hash (non-truncated SHA-256 or better)
  • StrongBox keystore provided by secure element
  • Hardware key attestation support for the StrongBox keystore
  • Attest key support for hardware key attestation to provide pinning support
  • Weaver disk encryption key derivation throttling provided by secure element
  • Insider attack resistance for updates to the secure element (Owner user authentication required before updates are accepted)
  • Inline disk encryption acceleration with wrapped key support
  • 64-bit-only device support code
  • Wi-Fi anonymity support including MAC address randomization, probe sequence number randomization and no other leaked identifiers
  • Support for disabling USB data and also USB as a whole at a hardware level in the USB controller
  • Reset attack mitigation for firmware-based boot modes such as fastboot mode zeroing memory left over from the OS and delaying opening up attack surface such as USB functionality until that’s completed
  • Debugging features such as JTAG or serial debugging must be inaccessible while the device is locked

  source

  • jjlinux@lemmy.zip ⁨3⁩ ⁨weeks⁩ ago

    I really hope GOS does find an OEM willing to throw the kitchen sink at this.

    source

    • artyom@piefed.social ⁨2⁩ ⁨weeks⁩ ago

      They already have. They won’t say who it is but it’s in the works.

      source

      • jjlinux@lemmy.zip ⁨2⁩ ⁨weeks⁩ ago

        Yeah, I’ve been following that up closely. Really looking forward to this.

        source
• Goodlucksil@lemmy.dbzer0.com ⁨3⁩ ⁨weeks⁩ ago

  The hardware security measures graphene wants are very expensive. Plus, GOS wants quick android security patche

  source
• weaponG@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  Even LineageOS would be amazing.

  source

  • jjlinux@lemmy.zip ⁨3⁩ ⁨weeks⁩ ago

    Agreed

    source