summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAdrian Roos <roosa@google.com>2017-09-05 15:09:42 +0000
committerAdrian Roos <roosa@google.com>2017-09-22 16:06:52 +0000
commitfd5927fdb7816674c8e631926676c079b06feeae (patch)
treea60acc97c841a8cfef08b6fbdf398be88fa6a64a
parentdb208f184b8bd153754834aecebcbc56094c7d26 (diff)
downloaddragon-fd5927fdb7816674c8e631926676c079b06feeae.tar.gz
FRP: disable credential FRP on dragon
Dragon's gatekeeper does not preserve the lockscreen credentials across a factory reset, therefore we cannot verify them during the FRP flow. Bug: 65258606 Change-Id: I2644b1c3ce54d36a2dfd4131465356e846df3124 Test: Verify that the FRP flow does not ask for the previous lockscreen credential on dragon
-rw-r--r--overlay/frameworks/base/core/res/res/values/config.xml7
1 files changed, 7 insertions, 0 deletions
diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index 1b13f00..9766de6 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -51,6 +51,13 @@
<!-- Enable device idle mode -->
<bool name="config_enableAutoPowerModes">true</bool>
+ <!-- If true, enables verification of the lockscreen credential in the factory reset protection
+ flow. This should be true if gatekeeper / weaver credentials can still be checked after a
+ factory reset.
+
+ dragon's gatekeeper does not preserve credentials across factory resets. -->
+ <bool name="config_enableCredentialFactoryResetProtection">false</bool>
+
<!-- Flag indicating whether the we should enable the automatic brightness in Settings.
Software implementation will be used if config_hardware_auto_brightness_available is not set -->
<bool name="config_automatic_brightness_available">true</bool>