summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEran Messeri <eranm@google.com>2018-06-22 12:56:44 +0100
committerEran Messeri <eranm@google.com>2018-06-22 12:56:44 +0100
commit4260ee9282f9666821dbdb4e7dda6c65f605a6b2 (patch)
treea449f3d4fb4395de867841cb27b8d12b6c53e042
parente203e04eeb438a58202bf632c617ef293af3093a (diff)
downloadnative-4260ee9282f9666821dbdb4e7dda6c65f605a6b2.tar.gz
AOSP builds do not support Device ID attestation
AOSP builds have different product & brand values than the ones flashed onto the device's Keymaster in the factory. As a result, Device ID attestation will not work on them correctly because there is a mismatch between the values sent to Keymaster by the platform and the values Keymaster is expecting to attest to. Mark AOSP builds as not having this feature since it would affect all AOSP builds on all devices. Bug: 110361822 Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement Change-Id: I55e7c68b3e082af465c19cf18aeeeecffc4eb356
-rw-r--r--data/etc/aosp_excluded_hardware.xml1
1 files changed, 1 insertions, 0 deletions
diff --git a/data/etc/aosp_excluded_hardware.xml b/data/etc/aosp_excluded_hardware.xml
index 013f278f34..c12f4358c5 100644
--- a/data/etc/aosp_excluded_hardware.xml
+++ b/data/etc/aosp_excluded_hardware.xml
@@ -18,4 +18,5 @@
<!-- This should be used to exclude this feature from aosp targets. As aosp configurations
may or may not have a valid location provider -->
<unavailable-feature name="android.hardware.location.network" />
+ <unavailable-feature name="android.software.device_id_attestation" />
</permissions>