| fe2d5ed8d79e52e989da1754f809bd6ff72de1bd |
|
02-Sep-2017 |
Fyodor Kupolov <fkupolov@google.com> |
Close idle connections to release RAM
Close idle connections after 30s of inactivity to release RAM.
Savings: ~0.4mb on marlin
Bug: 63398887
Test: reboot and dumpsys meminfo system
Change-Id: I39aa1fef9ae9850564a13891cb89c27cb805d683
/frameworks/base/services/core/java/com/android/server/locksettings/LockSettingsStorage.java
|
| 971f2948fbee3766ec01907f5a6e23f4c9bb4872 |
|
12-Jul-2017 |
Andrew Scull <ascull@google.com> |
Credential FRP: remove GateKeeper
From O-DR, all new credentials will be synthetic password based. A
GateKeeper credential could be enrolled but that would require
`adb shell cmd lock_settings sp 0`.
Credential FRP won't be released before O-DR so there is no need to
handle GateKeeper credentials. The protocol constants have been updated
because they are not yet in use.
Bug: 36814845
Test: runtest frameworks-services -p com.android.server.locksettings
Change-Id: Id0def06bb56fef47f3151f4f5cd0db738b35979f
/frameworks/base/services/core/java/com/android/server/locksettings/LockSettingsStorage.java
|
| 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/services/core/java/com/android/server/locksettings/LockSettingsStorage.java
|
| 4c870a095a94d42b796d59be1c89ed7abd645fe5 |
|
19-May-2017 |
Andrew Scull <ascull@google.com> |
Merge "Resolve error-prone warnings."
|
| 8fc2ec832f765a51c8fcd04cc89428a3ced4b605 |
|
19-May-2017 |
Andrew Scull <ascull@google.com> |
Resolve error-prone warnings.
Objects used for synchronisation should be final and inner classes
should be static, if possible.
Change-Id: I2be5bae504835660fad752048b2ab9c7076fafc0
Fix: 38442000
Test: Build
/frameworks/base/services/core/java/com/android/server/locksettings/LockSettingsStorage.java
|
| aa32d1530594db74e730e99d5ebbf8809bacd9d1 |
|
27-Apr-2017 |
Rubin Xu <rubinxu@google.com> |
Invoke BLKSECDISCARD to securely delete sensitive data
Bug: 34600579
Test: manual - change device lock under synthetic password, verify
old data on disk is erased.
Change-Id: I247bd1f095dd27335e671981f9e2d77e149af84f
/frameworks/base/services/core/java/com/android/server/locksettings/LockSettingsStorage.java
|
| 507d11c9353666a75fee014565f900825a907691 |
|
03-May-2017 |
Andrew Scull <ascull@google.com> |
Move LockSettingsService into locksettings package.
This service now has a large number of support classes so move them into
their own package to keep things tidy and easier to refactor.
Bug: 37090873
Test: runtest frameworks-services -c com.android.server.locksettings.LockSettingsServiceTests
Test: runtest frameworks-services -c com.android.server.locksettings.LockSettingsShellCommandTest
Test: runtest frameworks-services -c com.android.server.locksettings.SyntheticPasswordTests
Change-Id: Ic3cd00e6565749defd74498a3491c3d9b914ad90
/frameworks/base/services/core/java/com/android/server/locksettings/LockSettingsStorage.java
|