Hacker News new | ask | show | jobs
by codethief 73 days ago
> The initial limitation to Google/Android is not great, we know that, and we have support for other OSs on our list (like, e.g., GrapheneOS).

GrapheneOS uses standard Android APIs for hardware attestation (as opposed to Google-specific ones), so why don't you just use those from the get-go?

1 comments

They did. This is why Graphene works.
They said they have GOS support in the roadmap, meaning they know it doesn't work but pinky promise to work on it in some undisclosed future.
Call me confused. The comment I was responding to is saying something different:

> The initial limitation to Google/Android is not great, we know that, and we have support for other OSs on our list (like, e.g., GrapheneOS).

Yes, they still need to audit and whitelist the builds of GrapheneOS. That's what "standard APIs" are - they identify a build of OS, but someone still needs to make sure it's secure.

If you don't want Google to do that for you, then the app developer has to.