Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Fix comment in docs about ID attestation." am: 5592977b0f

Browse Source 
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2116413

Change-Id: Ia4a4520e7ac1b2fa038b4f366c84a8b6fd6ee8bf
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
Max Bires
2022-06-10 00:00:12 +00:00
committed by Automerger Merge Worker
parent a53421a150 5592977b0f
commit 215389da4b
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
core/java/android/os/Build.java
View File

@@ -165,9 +165,11 @@ public class Build {
* Gets the hardware serial number, if available. * Gets the hardware serial number, if available.
* *
* <p class="note"><b>Note:</b> Root access may allow you to modify device identifiers, such as * <p class="note"><b>Note:</b> Root access may allow you to modify device identifiers, such as
* the hardware serial number. If you change these identifiers, you can use * the hardware serial number. If you change these identifiers, you can not use
* <a href="/training/articles/security-key-attestation.html">key attestation</a> to obtain * <a href="/training/articles/security-key-attestation.html">key attestation</a> to obtain
* proof of the device's original identifiers. * proof of the device's original identifiers. KeyMint will reject an ID attestation request
* if the identifiers provided by the frameworks do not match the identifiers it was
* provisioned with.
* *
* <p>Starting with API level 29, persistent device identifiers are guarded behind additional * <p>Starting with API level 29, persistent device identifiers are guarded behind additional
* restrictions, and apps are recommended to use resettable identifiers (see <a * restrictions, and apps are recommended to use resettable identifiers (see <a