Conversation

Replying to and
Those apps are choosing to depend on Play Services and use SafetyNet attestation to verify that it's a certified release without tampering. The issue is ultimately apps choosing to do that not Google improving SafetyNet attestation to make it less trivial for attackers to bypass.
2
Auditor can only support OSes leaving the security model for attestation and verified boot intact. If there's a way to grant root access to the application layer, that's not compatible with the security model. Verified boot accomplishes little if persistence as root is supported.
1
The hardware-based attestation provides basic information on verified boot state, patch level, etc. The hardware-based attestation feature supports chaining trust through the OS to the app and for that to be meaningful it has to protect Auditor from tampering by other apps, etc.
1
The foundation of Auditor is that an attacker can't fake the hardware-based attestation information without exploiting the bootloader or secure element (or the TEE on lesser devices). OS level checks are given meaning by the hardware-based portion providing the patch level.
1
Show replies