The EU approach is not without its own problems. The reference code is open, but the operational system is not self-hostable. You cannot run your own trusted identity provider. The wallet apps require Google Play Services or the iOS equivalent, which locks out users of privacy-focused Android distributions like GrapheneOS, CalyxOS, and LineageOS. […]
ollama launch <your AI agentic frontend here> -- "Write me an age attestastion app for Android that implements EU's attestation reference framework without any bootloader checks."
The problem isn’t the software, there is already software that provides identity services.
The problem is that you will not have the cryptographic signatures that authenticate your app as a trusted identity provider. Nor would your app be able to fool the hardware attestation, which is built on unique signed cryptographic certificates that are signed by the manufacturer’s Certificate Authority and physically burned into the TPM on your device.
In order to pass attestation, your system must boot into a trusted OS image and then it has to prove that by submitting a signed quote, generated by information stored in your TPM along with keys signed by the manufacturer’s CA.
This isn’t something that you can hack around, it’s built on cryptographic verification of your entire boot sequence.
ollama launch <your AI agentic frontend here> -- "Write me an age attestastion app for Android that implements EU's attestation reference framework without any bootloader checks."The problem isn’t the software, there is already software that provides identity services.
The problem is that you will not have the cryptographic signatures that authenticate your app as a trusted identity provider. Nor would your app be able to fool the hardware attestation, which is built on unique signed cryptographic certificates that are signed by the manufacturer’s Certificate Authority and physically burned into the TPM on your device.
In order to pass attestation, your system must boot into a trusted OS image and then it has to prove that by submitting a signed quote, generated by information stored in your TPM along with keys signed by the manufacturer’s CA.
This isn’t something that you can hack around, it’s built on cryptographic verification of your entire boot sequence.