Auditor as example to use for hardware attestation
This commit is contained in:
parent
7ad211f93b
commit
9499523268
@ -74,6 +74,15 @@
|
|||||||
with hardware attestation and fall back to the Play Integrity API or do both and
|
with hardware attestation and fall back to the Play Integrity API or do both and
|
||||||
accept either passing as success.</p>
|
accept either passing as success.</p>
|
||||||
|
|
||||||
|
<p>Our <a href="https://github.com/GrapheneOS/Auditor">MIT / Apache 2 licensed Auditor
|
||||||
|
app</a> can be used a reference implementation for verifying hardware-based
|
||||||
|
attestations. There are some subtleties in the verification process such as making
|
||||||
|
sure only the 2nd certificate in the chain (the one signing the certificate for the
|
||||||
|
key generated by your app) has an attestation extension to prevent making a fake
|
||||||
|
attestation by extending the chain. You can reuse our code and simply omit support for
|
||||||
|
an app generated attestation signing key (attest key) and the other pinning
|
||||||
|
support.</p>
|
||||||
|
|
||||||
<p>After verifying the signature of the attestation certificate chain and extracting
|
<p>After verifying the signature of the attestation certificate chain and extracting
|
||||||
the attestation metadata, you can enforce that <code>verifiedBootState</code> is
|
the attestation metadata, you can enforce that <code>verifiedBootState</code> is
|
||||||
either <code>Verified</code> or <code>SelfSigned</code>. For the
|
either <code>Verified</code> or <code>SelfSigned</code>. For the
|
||||||
|
Loading…
x
Reference in New Issue
Block a user