10afa966fa
Currently Keystore is notified of the device being unlocked and locked for each user via onLockScreenEvent(lockScreenEvent, userId, password, unlockingSids), where lockScreenEvent is UNLOCK or LOCK. This is a bit confusing because the password parameter is only meaningful for UNLOCK, and the unlockingSids parameter is only meaningful for LOCK. This problem will get worse when we add a parameter that tells Keystore whether unlocking via a weak biometric or trust agent is possible, as that will be another parameter that is only meaningful for LOCK. Therefore, this CL splits onLockScreenEvent into two methods onDeviceUnlocked and onDeviceLocked, each with the appropriate parameters. No change in behavior intended. Bug: 296464083 Test: atest -p --include-subdirs system/security/keystore2 \ && atest CtsKeystoreTestCases \ && atest TrustTests \ && atest com.android.server.locksettings Flag: N/A, straightforward refactoring Change-Id: Ie2afd118bddca6112a5469558569c63b68ee10fb |
||
---|---|---|
.. | ||
legacy_blobs | ||
Android.bp | ||
AndroidTest.xml | ||
keystore2_client_3des_key_tests.rs | ||
keystore2_client_aes_key_tests.rs | ||
keystore2_client_attest_key_tests.rs | ||
keystore2_client_authorizations_tests.rs | ||
keystore2_client_delete_key_tests.rs | ||
keystore2_client_device_unique_attestation_tests.rs | ||
keystore2_client_ec_key_tests.rs | ||
keystore2_client_grant_key_tests.rs | ||
keystore2_client_hmac_key_tests.rs | ||
keystore2_client_import_keys_tests.rs | ||
keystore2_client_key_agreement_tests.rs | ||
keystore2_client_key_id_domain_tests.rs | ||
keystore2_client_keystore_engine_tests.rs | ||
keystore2_client_list_entries_tests.rs | ||
keystore2_client_operation_tests.rs | ||
keystore2_client_rsa_key_tests.rs | ||
keystore2_client_test_utils.rs | ||
keystore2_client_tests.rs | ||
keystore2_client_update_subcomponent_tests.rs |