| b15b1b4bd8fd1e7ccc2a243158aa55fe7623d15b |
|
06-Feb-2017 |
Andrew Scull <ascull@google.com> |
Schedule strong auth timeout in handler to avoid deadlock.
Bug: 34962180
Test: manual -- create profile, set separate password, remove separate
password and observe not deadlock i.e. screen doesn't freeze up.
Change-Id: I83b554ddeb22866d129de44775869d385e63fb3e
/frameworks/base/services/core/java/com/android/server/LockSettingsStrongAuth.java
|
| e71f583c782a98e977d6a5c450dff856b132e5c6 |
|
13-Jan-2017 |
Michal Karpinski <mkarpinski@google.com> |
Strong auth timeout refactor
Move timeout scheduling mechanism from KeyguardUpdateMonitor to
LockSettingsStrongAuth.
Move reporting about successful strong auth unlock from
KeyguardUpdateMonitor#reportSuccessfulStrongAuthUnlockAttempt()
to LockSettingsService#doVerifyCredential() - the latter also
covers work challenge strong auth unlocking.
Test: manual with all types of strong and non-strong auth, including work challenge
Bug: 29825955
Change-Id: I38e51b21e3a455b95e3c857e091fe07ee388c7f8
/frameworks/base/services/core/java/com/android/server/LockSettingsStrongAuth.java
|
| a7aa4d6f0b91e050c083c19459b0c8b265c92617 |
|
20-Jan-2016 |
Rakesh Iyer <rni@google.com> |
Allow smart unlock right after boot.
This change enables relaxing the constraint by which
strong authentication is needed after device reboot.
There are very limited use cases where this might be
safe, one of which is in a car. Cars head units usually
are protected physically by the car and have hardware
anti-theft mechanisms so we can potentially allow for
Android to allow users to use smart unlock to avoid the
lockscreen just after boot.
This change adds in a config flag that sets the default
trust flags, which can be set to allow smart unlock after
boot for car head units.
Bug: 26559008
Change-Id: Id6338a97b617ddaf3d2fae5d51235429a42b81cc
/frameworks/base/services/core/java/com/android/server/LockSettingsStrongAuth.java
|
| 7c69636c9a406265e1da368f3edfd8fb9651132c |
|
16-Sep-2015 |
Xiaohui Chen <xiaohuic@google.com> |
Cleanup USER_OWNER in various services
Bug: 19913735
Change-Id: I980370bab18e1b9ccf4043eed2b9fd721a940f72
/frameworks/base/services/core/java/com/android/server/LockSettingsStrongAuth.java
|
| b5e4722891e7bbf2fffcd995af02838667a3abab |
|
15-Aug-2015 |
Adrian Roos <roosa@google.com> |
Add StrongAuthTracker
Bug: 22846469
Bug: 22115393
Change-Id: I6ef5322d02e540fc043e7f20d3aabf595ce7c224
/frameworks/base/services/core/java/com/android/server/LockSettingsStrongAuth.java
|