From 0fb946acae29a027f048a3c15d71faec3243aaf4 Mon Sep 17 00:00:00 2001 From: Eric Biggers Date: Fri, 4 Aug 2023 21:27:49 +0000 Subject: Improve the LockSettingsService class comment Test: N/A Change-Id: I20d209b634fa1a45008273b242f72efb7673e7a6 --- .../server/locksettings/LockSettingsService.java | 37 ++++++++++++++++++++-- 1 file changed, 34 insertions(+), 3 deletions(-) diff --git a/services/core/java/com/android/server/locksettings/LockSettingsService.java b/services/core/java/com/android/server/locksettings/LockSettingsService.java index a4d08b06d620..af66bef7ae59 100644 --- a/services/core/java/com/android/server/locksettings/LockSettingsService.java +++ b/services/core/java/com/android/server/locksettings/LockSettingsService.java @@ -195,9 +195,40 @@ import javax.crypto.SecretKey; import javax.crypto.spec.GCMParameterSpec; /** - * Keeps the lock pattern/password data and related settings for each user. Used by - * LockPatternUtils. Needs to be a service because Settings app also needs to be able to save - * lockscreen information for secondary users. + * LockSettingsService (LSS) mainly has the following responsibilities: + *

+ *

+ *

+ * The main clients of LockSettingsService are Keyguard (i.e. the lockscreen UI, which is part of + * System UI), the Settings app (com.android.settings), and other parts of system_server. Most + * methods are protected by ACCESS_KEYGUARD_SECURE_STORAGE which only system processes can have. * * @hide */ -- cgit v1.2.3-59-g8ed1b