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…

  • ryannathans@aussie.zone
    21·
    10 days ago

    Bare in mind the chipset is the Google Tensor G4, they already had to design and build their own hardware. We don’t know everything it can do

    • Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.comEnglish
      1·
      10 days ago

      We don’t know everything it can do

      Neither do we know this about any other CPU on the market. All chipsets on the market are proprietary. All of them. And no, despite many people (who don’t know anything about what they are talking about) claiming this, RISC-V won’t actually solve any of these issues. Sure, the ISA is open source, but the ISA would be the worst place for malicious actors to introduce a backdoor. I can guarantee you that despite using the RISC-V ISA, the chips themselves will still be fully proprietary and the IP will be highly protected as trade secrets. You can build a fully RISC-V conformant chip with a backdoor, there’s absolutely nothing in place that could stop this, and it surely won’t change for the forseeable future.