| cc70155f3bf18341296aaa2163bd2e7df6997b11 |
|
17-May-2016 |
Paul Crowley <paulcrowley@google.com> |
Two phases to set the password for disk encryption
Revert "Revert "Two phases to set the password for disk encryption""
This reverts commit a1eb750e75ff7c7ef7698deed4442449c33334c8.
Bug: 28154455
Bug: 28694324
Change-Id: I8106bfba28da401b9fd38349c6a9fa9a24f54712
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| a1eb750e75ff7c7ef7698deed4442449c33334c8 |
|
10-May-2016 |
Paul Crowley <paulcrowley@google.com> |
Revert "Two phases to set the password for disk encryption"
This reverts commit 17e5dce5112fece2d2b9cd070c2f96bf65108e40.
Bug: 28694324
Change-Id: I6d89bc26cb429b195c9bcf640666c495617257b7
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| 17e5dce5112fece2d2b9cd070c2f96bf65108e40 |
|
22-Apr-2016 |
Paul Crowley <paulcrowley@google.com> |
Two phases to set the password for disk encryption
In one phase, we make the new password work, and in the second we make
it the only one which works ("fixation"). This means that we can set
the password in Gatekeeper between these two phases, and a crash
doesn't break things. Unlocking a user automatically fixates the
presented credential.
Bug: 28154455
Change-Id: I18812f9ce753486ce4e33b4fe2cca392b006b39c
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| a46b40fd5c3603b59c4a0d5d5fa4b0547fc26aff |
|
31-Mar-2016 |
Ricky Wai <rickywai@google.com> |
Add tests for profile keys in LockSettingsStorage
Bug: 27940135
Change-Id: Iade153f6607db4c75385bed6f20d3120c10674b0
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| dc283a897680ffd33c4d15535ebe778ba5b42c43 |
|
24-Mar-2016 |
Ricky Wai <rickywai@google.com> |
Keymaster init for work profile
Changes:
(1) When unified work challenge is enabled and screen lock is secure
- Store work profile secure key in primary profile
- When primary user keystore unlocked, unlock work profile keystore
- When primary user change lock to none, remove work secure key
(2) When unified work challenge is enabled but screen lock is not secure
- When screen lock changes to secure, store work secure key in primary
(3) When user changes work challenge from unified to separated
- Remove work secure key in primary
(4) When user changes work challenge from separate to unified
- Do (1) and (2)
Bug: 27460698
Change-Id: I8f77bde5dc6b8e59c90256e75c5990100e93366b
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| a1771110d67fa7361f92d92f2e91019882ce3305 |
|
18-Dec-2015 |
Clara Bayarri <clarabayarri@google.com> |
Create Work Challenge per-user condition
Change the current static condition to a per-user condition so we
can check and enable/disable the work challenge properly. Also add
an isAllowed API, as the Work Challenge can only be used when the
user's DPC targets N or above to maintain backwards compatibility.
Change-Id: I0cb8b475838816801868ffb24726407aa257b4de
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| 10ad84a17d7248488c1653bacc9f20d3a7193999 |
|
01-Dec-2015 |
Clara Bayarri <clarabayarri@google.com> |
Create a separate Work Challenge check
This allows us to tell lock checks from FBE checks separately,
and will be useful when dealing with password unification.
Change-Id: Ifbea425f749fee4d6d51faddd8b64bf717a1a5f8
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| ba51235ef5c598d845b77fcf14491329493da34f |
|
13-Nov-2015 |
Jeff Sharkey <jsharkey@android.com> |
More file-based encryption work.
Add new "am unlock-user" command so we can trigger changes from the
command line.
Move FBE check to static method so it can safely be called early
during boot before the mount service is ready. Move FBE emulation
to persisted system property, and start reading/writing that value.
Change default permission grants to ignore current encryption-aware
flags, since many of the target apps aren't crypto aware.
Always prepare package data directories, which is how we create the
new "user_de" paths during boot.
Bug: 22358539
Change-Id: I6f58ea2d34b3a466d3775d614f8a13de92272621
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| 965da39942f9a8736f785f7c57a6c351a8c89d6b |
|
28-Oct-2015 |
Clara Bayarri <clarabayarri@google.com> |
Create a File Based Encryption check API
Change-Id: Ibf41f98818ea801b9f690200c340be80c3b9bf31
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| 07b668e3abbc752028e92759b9b55ecf63fc91c3 |
|
13-Oct-2015 |
Clara Bayarri <clarabayarri@google.com> |
Enable Work Profile passphrase verify/write with FBE
When File Based Encryption is present, allow the verify/write of
passphrases to be per-user (it used to always bubble up to the parent
user assuming it is a per-device passphrase).
This is part of the work for the Separate Work Challenge.
Change-Id: I5ae6b7b6ed1dd25aed0843d495b6f5f36e01c4eb
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| e40bad8cf9397becdf05776c775c8286d3de46fa |
|
28-May-2015 |
Andres Morales <anmorales@google.com> |
[LockSettings] migrate patterns to be indexed at '1'
Base zero patterns (ones where the top left is idx 0)
are not handled properly by scrypt. Add logic to re-enroll
base zero patterns such that the top left is idx 1.
Bug: 21433955
Change-Id: I7f67f2c67d40dd1be6c62117710dc3b0392275a2
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| 8fa5665f0e757cec0063fb4cf1354f1596f93a91 |
|
31-Mar-2015 |
Andres Morales <anmorales@google.com> |
Wire up GateKeeper to LockSettingsService
Adds:
- Communication to GKService
- password upgrade flow
- enroll takes previous credential
Change-Id: I0161b64642be3d0e34ff4a9e6e3ca8569f2d7c0a
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| 68e4ba4dd0412f7923d3c22c92ebae485fc89961 |
|
10-Mar-2015 |
Robin Lee <rgl@google.com> |
Move more file handling into LockSettingsStorage
Strengthens the guarantee of only one kind of lock type existing at one
time by clearing all of the relevant files out closer to time of write.
Change-Id: I141103dab5d7d4bc80b05a22b8566326d1c9e7e1
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| e542499a304f067372d85722e11a74b4e56b0bd7 |
|
07-Nov-2014 |
Adrian Roos <roosa@google.com> |
Add LockSettingsStorage tests
Bug: 18163444
Change-Id: I563276e6d445d43d05bf0d3c633440a8e0109b69
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| 3dcae68501a1fc1c433d12a9d55a31c7eaab016c |
|
29-Oct-2014 |
Adrian Roos <roosa@google.com> |
Add caching to LockSettingsStorage
Bug: 18163444
Change-Id: I4caa80ca55efec761e965807ae793db41864321f
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|
| 261d5ab8f4c3fdd34163468fd48ab07f7ad13d3c |
|
29-Oct-2014 |
Adrian Roos <roosa@google.com> |
Refactor LockSettingsService into storage and logic
Creates a new LockSettingsStorage class to handle
stroring and retreiving data.
Bug: 18163444
Change-Id: Ia3bc4ad679c5e1217756ae6b3b80cfce3599baed
/frameworks/base/services/core/java/com/android/server/LockSettingsStorage.java
|