| 7374d3a4bca6bfbf7da1ef5dbf0db9f35f0c8315 |
|
31-Mar-2017 |
Adrian Roos <roosa@google.com> |
Credential FRP: Add implementation
- Adds a facility to store a credential handle that survives factory reset
- Adds a method to KeyguardManager for verifying the stored credential for SetupWizard
- Dark launches persisting the primary user's credential as the FRP credential (behind a default-off flag)
Future work:
- Use a separate GK handle / synthetic password for the FRP credential
- Enroll the FRP credential in verifyCredential for the upgrade case
Bug: 36814845
Test: runtest -x core/tests/coretests/src/com/android/internal/widget/LockPatternUtilsTest.java && runtest -x services/tests/servicestests/src/com/android/server/LockSettingsStorageTests.java && runtest -x services/tests/servicestests/src/com/android/server/SyntheticPasswordTests.java
Change-Id: Ia739408c5ecb169e5f09670cd9ceaa7febc2b1cc
/frameworks/base/core/java/android/service/persistentdata/IPersistentDataBlockService.aidl
|
| 74e9b18b2de2127e081b170cdd4622193cfb7543 |
|
22-Feb-2016 |
Andres Morales <anmorales@google.com> |
Add SystemApi for retrieving device flash lock state
Bug: 26039090
Change-Id: Ib51c4862d897cc91a0788379c761ed49a2adf271
/frameworks/base/core/java/android/service/persistentdata/IPersistentDataBlockService.aidl
|
| 09ad6bfe9619ff7a61209131f1f3182d53d840d0 |
|
02-Jun-2015 |
Craig Lafayette <craiglafa@google.com> |
Remove FRP wipe support for device initializers
- Remove ManagedProvisioning NFC parameter key from
DevicePolicyManager
- Remove wipeIfAllowed from PersistentDataBlockManager
Bug: 21558883
Change-Id: I59354b7bb1ef7e0b0346ff9a7d1654780231dff0
/frameworks/base/core/java/android/service/persistentdata/IPersistentDataBlockService.aidl
|
| 66445a639dc134d09393f5069b7683ec36d4cd07 |
|
27-Mar-2015 |
Craig Lafayette <craiglafa@google.com> |
Reset protection in PersistentDataBlockManager
Add method to allow authorized data block wipe in support of factory
reset protection. This will allow ManagedProvisioning to respond to
and pass factory reset protection challenges during automated device
setup.
- Adds the wipeIfAllowed method to clear the data block
- Creates a protected-broadcast to send to allowed package
Bug: 19792435
Change-Id: I897f2ea2afb1222a1fc8ac49290ee45ea4d3f2d7
/frameworks/base/core/java/android/service/persistentdata/IPersistentDataBlockService.aidl
|
| 963295ea105314e28e4ca9563aa09cb7440de4c3 |
|
11-Jul-2014 |
Andres Morales <anmorales@google.com> |
Permit settings to "wipe" the persistent partition
One of the requirements is that when the user does a
factory reset through settings, all data on the
persistent partition should be cleared.
This adds one last API method that allows settings
to wipe the partition.
Bug: 14288780
Change-Id: Ib87ee741d1e5195814516ae1d66eb7c4cf754dcf
/frameworks/base/core/java/android/service/persistentdata/IPersistentDataBlockService.aidl
|
| 68d4acd205e8c2da524e62734ca42847306cc029 |
|
02-Jul-2014 |
Andres Morales <anmorales@google.com> |
Service for reading and writing blocks to PST partition
Permits apps with permission
android.permission.ACCESS_PERSISTENT_PARTITION to obtain
a read and write data blocks to the PST partition.
Only one block ever exists at one time in PST. When
a client writes another block, the previous one is
overwritten.
This permits storing a block of data that will live
across factory resets.
Change-Id: I8f23df3531f3c0512118eb4b7530eff8a8e81c83
/frameworks/base/core/java/android/service/persistentdata/IPersistentDataBlockService.aidl
|