GrapheneOS attestation compatibility guide
grapheneos.org
Guide on using remote attestation in a way that's compatible with GrapheneOS.

cross-posted from: https://slrpnk.net/post/15995282

Real unfortunate news for GrapheneOS users as Revolut has decided to ban the use of ‘non-google’ approved OSes. This is currently being posted about and updated by GrahpeneOS over at Bluesky for those who want to follow it more closely.

Edit: had to change the title, originally it said Uber too but I cannot find back to the source of ether that’s true or not…

  • Realitaetsverlust@lemmy.zipEnglish
    36·
    1 month ago

    It’s only officially supported on google phones because sadly those are the only ones that are not modified to fuck which makes installing and supporting other OS’es way too much work.

    Giving google money once for a device is not a problem from a privacy or security standpoint.

    • Samsy@lemmy.ml
      12·
      1 month ago

      That’s correct, but not the reason grapheneOS chooses only pixel phones. It’s the level of hardware security features.

      • XTL@sopuli.xyz
        2·
        1 month ago

        Also unlockable and presumably has well working builds. It’s not just graphene, but just about every Android project it there that’s best supported on pixels. Other manufacturers have a crazy variety of locking schemes and required tools. Each one is a nightmare to support.

        • orange@communick.news
          1·
          1 month ago

          For GrapheneOS, it’s primarily that it’s re-lockable. That’s why other unlockable phones aren’t supported.

          The GrapheneOS install process sets new OS signing keys so you can lock the phone again and get full verified boot. However, most manufacturers haven’t implemented this feature.