1cb6f9d8a4827d50e26bf83068a928e47c5c1f1e |
|
26-May-2016 |
Ricky Wai <rickywai@google.com> |
Merge "Add resetKeyStore() in LockSettingsService" into nyc-dev
|
4613fe41ac9e817e76d7087de45bf01f4a6584d6 |
|
24-May-2016 |
Ricky Wai <rickywai@google.com> |
Add resetKeyStore() in LockSettingsService Before resetKeyStore(), it will back up child profile keys, and will be restored after primary profile keystore is cleared. Bug: 28878708 Change-Id: I0cb4a1f885d468894bc7eb95af694328bf92ce16
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
a0940d33dcbac0245ad5467d9c302f8eaee615dc |
|
16-May-2016 |
Victor Chang <vichang@google.com> |
New api in LockSettingsService to get StrongAuth synchronously Not all client needs to monitor the StrongAuth, e.g. ConfirmDeviceCredentialBaseFragment Provide a quick method to get StrongAuth Bug: 28752364 Change-Id: Iecfd217046da38e43297bdd5832cf7d637b979ed
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
4ab7e595a5deef72448da950f2f973bc0c90fe18 |
|
14-Apr-2016 |
Adrian Roos <roosa@google.com> |
StrongAuthTracker: Don't rely on USER_PRESENT USER_PRESENT is sent via the background queue. A delay there can cause us not to recognize that the user has unlocked and prompt for the credential again, when trust or fingerprint would be sufficient. Also removes an obsolete reference to USER_PRESENT from TrustManagerService. Change-Id: Ie8d1a180170df5f0c8f9e71660504fd71eeacd99 Fixes: 27830458
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
53940d4c7f45a26d8b571982a1f8f4b8094aa5e0 |
|
05-Apr-2016 |
Ricky Wai <rickywai@google.com> |
Fingerprint should confirm device lock when unified When unified and adding a fingerprint, the user is prompted to set up a backup Bug:27419438 Change-Id: I3e857fa07c50ee0904f685b721595ef6cfe729f9
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
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/core/java/com/android/internal/widget/ILockSettings.aidl
|
4f93c58b393bad5d0bcc4237fa66f14fb9c9ee28 |
|
28-Jan-2016 |
Jim Miller <jaggies@google.com> |
Add account locked notification when users are encrypted Fixes bug 26407543 Change-Id: Ic66669cd5f75b5fa41449e33133439752cef112b
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
b5e4722891e7bbf2fffcd995af02838667a3abab |
|
15-Aug-2015 |
Adrian Roos <roosa@google.com> |
Add StrongAuthTracker Bug: 22846469 Bug: 22115393 Change-Id: I6ef5322d02e540fc043e7f20d3aabf595ce7c224
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
2397427cb1a0bad8a42e6a342dcf29b31e40a234 |
|
15-May-2015 |
Andres Morales <anmorales@google.com> |
[LockSettings] migrate password attempt throttling to hardware leverage root protected, cryptographically secured hardware if available Bug: 21118563 Change-Id: Ifa804c5a0728bfd14466eb2a84051bace6d33d57
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
d9fc85ac27742adbe89e54fd35f3cb2469e94b91 |
|
10-Apr-2015 |
Andres Morales <anmorales@google.com> |
Add challenge to IGateKeeperService required for enrolling secondary auth form-factors Change-Id: Id5a1eb1ed22f01fbaabe8e4ebddfc42d58322625
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
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/core/java/com/android/internal/widget/ILockSettings.aidl
|
db0f76e1d85f8cb878a9540ac1b692636f9fd89e |
|
07-Jan-2015 |
Adrian Roos <roosa@google.com> |
Directly dispatch USER_REMOVED to LockSettingsService Bug: 18931518 Change-Id: Ibaf875a06868ae3196115d77eed6874daf2fec16
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
138b83347b8da29166ee2eb09fa8126686bda3c7 |
|
11-Nov-2014 |
Adrian Roos <roosa@google.com> |
Obliterate LockPatternUtilsCache It is disabled dead code already and not useful anymore with the new caching in LockSettingsService. Bug: 18163444 Change-Id: Icc184e923e0fbeab31ed128336c01f835b24c6f2
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
4f7884542ce8fba5bfed01ed834a32e6d3e2dea5 |
|
22-May-2014 |
Adrian Roos <roosa@google.com> |
Add a cache to LockPatternUtils Caches responses from LockSettingsService in the client process. Bug: 15088101 Change-Id: If77c5ec45f52a02c800d50cb8550bfcb180f301d
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
945490c12e32b1c13b9097c00702558260b2011f |
|
27-Mar-2014 |
Paul Lawrence <paullawrence@google.com> |
Don't double prompt on booting encrypted device vold will store password securely until KeyGuard requests it and hands it on to KeyStore. This is a revision of https://googleplex-android-review.git.corp.google.com/#/c/418123/ which was reverted. It had two bugs in LockSettingsService.checkVoldPassword. 1) We were not checking password for null, which caused an exception 2) checkPattern/checkPassword return true if there is no saved pattern or password. This leads to situations where we get true returned even when the password doesn't match. Call the correct one based on what is there, not what vold thinks ought to be there. Bug: 12990752 Change-Id: I05315753387b1e508de5aa79b5a68ad7315791d4
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
6ee7d25010d4f23b44a151f3953225ba253de8af |
|
26-Mar-2014 |
Paul Lawrence <paullawrence@google.com> |
Revert "Don't prompt at boot if we already did that when decrypting" This reverts commit 493e3e7e6523fd94cc1acae3e45935a1227d58c3. Should fixes Bug: 13611885 Bug: 13656830 Change-Id: I117c988bb6679f44f8add4fcc18f45cb8238dfb4
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
493e3e7e6523fd94cc1acae3e45935a1227d58c3 |
|
06-Feb-2014 |
Paul Lawrence <paullawrence@google.com> |
Don't prompt at boot if we already did that when decrypting vold will store password securely until KeyGuard requests it and hands it on to KeyStore. Needs matching vold changes from https://googleplex-android-review.git.corp.google.com/#/c/432050/ Bug: 12990752 Change-Id: I930ed8180cf0b8feb1e58db043d5fb6dff1bab20
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
de1af08dd3a073f007ae4b8a114352cae3775028 |
|
11-Sep-2013 |
Jim Miller <jaggies@google.com> |
Fix keyguard/Keystore storage issue Keystore stored keys broke when keyguard was moved out of the system process due to Keystore enforcing the calling app to be in the system process. The fix moves the critical code into LockSettingsService, which continues to live in the system process. Fixes bug 10201270 Change-Id: I16e2de018e85b01265634dcfbefd7f06740dafa8
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|
52c489cd63cca0361f374f7cb392018fabfa8bcc |
|
28-Mar-2012 |
Amith Yamasani <yamasani@google.com> |
Lockscreen settings per user Move all lockscreen related settings to LockSettingsService. LockPatternUtils uses this through IPC instead of Secure settings. Migrate old settings to new database managed by LockSettingsService. Passwords and patterns are stored in a new per-user location, except for the primary user, for backward compatibility. KeyguardViewMediator and LockPatternKeyguardView listen for changes to user and updates the lockscreen. Settings provider will look for Lock settings in the LockSettings service now for the entries that used to be stored in Settings. Change-Id: I956cd5b95e2d9d45a6401af7e270e6a5aa2dcc98
/frameworks/base/core/java/com/android/internal/widget/ILockSettings.aidl
|