Anarchist without adjectives
Sysadmin into Linux, Selfhosting and Piracy

  • 0 Posts
  • 8 Comments
Joined 3M ago
cake
Cake day: Jan 03, 2026

help-circle
rss

Having read the comments I still see two major isssues with this:

  1. This looks like an almost-as-secure-as-GrapheneOS fork, therefore creating a (false) sense of security, because…
  2. GrapheneOS’s security is based on secure hardware (Pixel’s Titan chip) to verify the software. Only having software security without the underlying secure hardware is kind of pointless or at least well… a false sense of security.

Officially yes, but I suspect he is still behind the official social media accounts. Their tone is unchanged and I recently got blocked by the GOS account on Bluesky and immediately by Micay’s account as well.


I think it’s a lot more than just 3 features removed. AFAIK the whole hardware attestation is based on the Titan chip and you don’t have to trust the devices hardware, because you can cryptographically prove that the software is unchanged. It’s not only about the Auditor app, but the whole integrity of the OS, the boot process and firmware is secured by the Pixel’s hardware or more specific the Titan chip.

And the billions of devices can not be saved by a GrapheneOS fork because they’re mostly missing crucial firmware and generally get no updates anymore. That’s why GrapheneOS is only supporting recent devices and especially Pixel devices because they receive up to 7 years updates.

I’m all into getting people a more secure OS but I fear that a GrapheneOS fork is perceived as a secure OS when it’s actually not. The most important security features are still recent (firmware) updates and hardware attestation, verified boot etc.