Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit eb6124cb authored by Kevin Hufnagle's avatar Kevin Hufnagle Committed by android-build-merger
Browse files

Merge \\"docs: Added note about limited support for hardware key... 

Merge \\"docs: Added note about limited support for hardware key attestation\\" into nyc-dev am: 68b98bc6
am: 6198b6cd

Change-Id: Icce0f6f456fddc098597b7f656db368733250583
parents b604ade4 6198b6cd

docs/html/preview/api-overview.jd

+14 −0
Original line number Diff line number Diff line
@@ -755,6 +755,20 @@ For more information, see <a href="{@docRoot}preview/features/direct-boot.html"> 
  on the device.

</p>



<p class="note">

  <strong>Note: </strong>Only a small number of devices running Android N

  support hardware-level key attestation; all other devices running Android N

  use software-level key attestation instead. Before you verify the properties

  of a device's hardware-backed keys in a production-level environment, you

  should make sure that the device supports hardware-level key attestation. To

  do so, you should check that the attestation certificate chain contains a root

  certificate that is signed by the Google attestation root key and that the

  <code>attestationSecurityLevel</code> element within the <a

  href="{@docRoot}preview/features/key-attestation.html#certificate_schema_keydescription">key

  description</a> data structure is set to the TrustedEnvironment security

  level.

</p>



<p>

  For more information, see the

  <a href="{@docRoot}preview/features/key-attestation.html">Key Attestation</a>

docs/html/preview/features/key-attestation.jd

+15 −2
Original line number Diff line number Diff line
@@ -21,6 +21,19 @@ page.keywords="android N", "security", "TEE", "hardware-backed", "keystore", "ce 
  interpret the schema of the attestation certificate's extension data.

</p>



<p class="note">

  <strong>Note: </strong>Only a small number of devices running Android N

  support hardware-level key attestation; all other devices running Android N

  use software-level key attestation instead. Before you verify the properties

  of a device's hardware-backed keys in a production-level environment, you

  should make sure that the device supports hardware-level key attestation. To

  do so, you should check that the attestation certificate chain contains a root

  certificate that is signed by the Google attestation root key and that the

  <code>attestationSecurityLevel</code> element within the <a

  href="#certificate_schema_keydescription">key description</a> data structure

  is set to the TrustedEnvironment security level.

</p>



<h2 id="verifying">

  Retrieving and Verifying a Hardware-backed Key Pair

</h2>
@@ -227,8 +240,8 @@ VerifiedBootState ::= ENUMERATED { 
      level</a> of the attestation.

    </p>



    <p class="note">

      <strong>Note:</strong> Although it is possible to attest keys that are

    <p class="caution">

      <strong>Warning:</strong> Although it is possible to attest keys that are

      stored in the Android system&mdash;that is, if the

      <code>attestationSecurity</code> value is set to Software&mdash;you

      cannot trust these attestations if the Android system becomes compromised.