| c6cd327ccd458eec4187d491b73551a7c4bcd6cb |
|
19-Mar-2015 |
Andres Morales <anmorales@google.com> |
Write correct checksum when formatting partition
OEM unlock enabled bit is not computed in the checksum,
causing OEM Unlocking to be disabled after the second
reboot.
Bug: 19829441
Change-Id: I100bf5d3958b89323ee35b9e97b19c162209fcd7
/frameworks/base/services/core/java/com/android/server/PersistentDataBlockService.java
|
| 1ce7d179bf00a9ebebef8aff0006d71469870c26 |
|
07-Jan-2015 |
Andres Morales <anmorales@google.com> |
Wipe FRP partition if OEM unlock enabled
Not all devices invoke recovery on every userdata wipe,
so we can't rely on code in the
recovery OS to do this. This results in fastboot -w
not properly wiping the FRP partition. This patch
fixes the issue by having the framework level service
check the OEM unlock enabled bit, and wiping the partition
if it is set.
Bug: 18644051
Change-Id: Id97a29916fe39561700912a920c5741109842bdb
/frameworks/base/services/core/java/com/android/server/PersistentDataBlockService.java
|
| 6b0c7acd7f175552d90d1d73b9717ff347158e7d |
|
24-Nov-2014 |
Andres Morales <anmorales@google.com> |
Define permission for system apps to query size of block
Allows ManagedProvisioning to determine whether there's a
challenge and thus whether to disable NFC provisioning.
Other implementation option: new hidden boolean API method.
Can't think of benefit of new API method "isBlockInUse", other
than doesn't leak PDB size and is more explicitly tied to the
use case. Open to either impl if anyone has opinions on the matter.
Bug: 18508767
Change-Id: I28d2eb5a0837ff85cb91f140b17ce1dd843fe9d6
/frameworks/base/services/core/java/com/android/server/PersistentDataBlockService.java
|
| 2830130770b0d010007d126f64756413f922974b |
|
12-Nov-2014 |
Andres Morales <anmorales@google.com> |
Add a checksum to FRP partition
It will be hard to mandate the contents
of the FRP partition out of factory. Further, for upgrading
units, it would require that OEMs format the partition and then store
a bit saying that they've done so. This adds another attack vector.
Now defeating FRP means either compromising the FRP partition
OR wherever the OEMs decide to store that bit.
This patch adds a checksum to the FRP partition. If the checksum
is not valid, the partition is wiped - disabling OEM unlock.
This ensures that no matter what data comes on the partition, we will
always disable OEM unlock by default. It also allows OEMs to not have to
worry about initializing the partition, as it happens automatically.
Bug: 18322021
Change-Id: Ib30782baa771591c30ea95054d3b83f36fc08cc2
/frameworks/base/services/core/java/com/android/server/PersistentDataBlockService.java
|
| a31c23da300b5d1f4b1fc261bb0dcb1fee9b61f1 |
|
30-Oct-2014 |
Andres Morales <anmorales@google.com> |
Only allow USER_OWNER to access PDB and change OEM unlock ability
Bug:18191568
Change-Id: Ie09823945af04accead99216580efc958bf6aefe
/frameworks/base/services/core/java/com/android/server/PersistentDataBlockService.java
|
| 514c58045980998909883bfed5810c9508fd2f7b |
|
13-Sep-2014 |
Guang Zhu <guangzhu@google.com> |
do not allow monkey to flip OEM unlock flag
Bug: 11435021
Change-Id: I3a6865bc6c9fde245d8f4af3230716eac4a3f1b1
/frameworks/base/services/core/java/com/android/server/PersistentDataBlockService.java
|
| 6429f313b4248a010bb197993bbdb16629459d69 |
|
05-Aug-2014 |
Andres Morales <anmorales@google.com> |
Allow PersistentDataBlockService to be used with all users
Bug: 16795591
Change-Id: Id5e5dc5c26408752fe85f6f6fc2c67d9408b6a2a
/frameworks/base/services/core/java/com/android/server/PersistentDataBlockService.java
|
| 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/services/core/java/com/android/server/PersistentDataBlockService.java
|
| 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/services/core/java/com/android/server/PersistentDataBlockService.java
|