summaryrefslogtreecommitdiffstats
path: root/core/java/com/android/internal/widget/LockPatternUtils.java
Commit message (Collapse)AuthorAgeFilesLines
* LockPatternUtils: userId is requiredWolfgang Wiedmeyer2016-12-161-2/+2
| | | | Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
* support separate encryption/lockscreen passwordsDaniel Micay2016-12-161-3/+69
| | | | | | | | | | | | This adds the necessary infrastructure for allowing users to opt-in to a distinct device encryption passphrase. The passwords are still tied together by default. This makes it possible to use a complex encryption passphrase without losing the convenience of a very simple lockscreen pin. This feature can be combined with a forced reboot after a chosen number of failed unlocking attempts to prevent brute-forcing by requiring the entry of the encryption password instead.
* Merge tag 'android-6.0.1_r72' into HEADJessica Wagantall2016-10-061-2/+2
|\ | | | | | | | | | | | | Android 6.0.1 Release 72 (M4B30X) # gpg: Signature made Tue 04 Oct 2016 09:47:40 AM PDT using DSA key ID 9AB10E78 # gpg: Can't check signature: public key not found
| * Fix vulnerability in LockSettings serviceJim Miller2016-08-261-2/+2
| | | | | | | | | | | | | | Fixes bug 30003944 Change-Id: I8700d4424c6186c8d5e71d2fdede0223ad86904d (cherry picked from commit 2d71384a139ae27cbc7b57f06662bf6ee2010f2b)
* | LockPatternUtils: Use the actual user id to set pattern sizeScott Mertz2016-04-141-10/+10
| | | | | | | | | | Ticket: CYNGNOS-2462 Change-Id: Ia68e26ec2dfc23317135d933bc25204c1380bb02
* | Merge tag 'android-6.0.1_r22' of ↵Steve Kondik2016-03-111-0/+18
|\ \ | | | | | | | | | | | | | | | | | | | | | https://android.googlesource.com/platform/frameworks/base into cm-13.0 Android 6.0.1 release 22 Change-Id: I0d31899b234156a91accb61e0a7fb3d8d16d5062
| * | Allow access to deprecated LOCK_PATTERN_ENABLED flag.Bryce Lee2015-12-141-0/+18
| |/ | | | | | | | | | | | | | | | | | | | | It is possible that older platforms may have not cleared the lock pattern, but instead only checked this flag to determine the lock pattern enabled state. In such cases, upgrading to a platform with that only checks the lock pattern can lead to the lock screen being re-enabled by accident. These new methods allow this condition to be identified and resolved. Bug: 26029690 Change-Id: I8f7ebc0e1915049afe49c219c87010aa38a16244
* | Fix pattern visibility settings (1/2)Michael Bestas2016-02-031-8/+8
| | | | | | | | Change-Id: Ic627953c5df854c442671a98b5da539b994da18b
* | LockPatternUtils: Make settings getter and setters protectedd34d2015-12-111-6/+6
| | | | | | | | | | | | | | | | This patch will allow us to extend LockPatternUtils in the cmsdk and have access to getting and setting lock settings, and minimize code changes to the original LockPatternUtils class. Change-Id: I3417f64db1f05cffab47328df574f23dd20776d5
* | Forward port CM Screen Security settings (1/2)Michael Bestas2015-12-111-8/+57
| | | | | | | | | | | | | | * Variable size pattern lockscreen * Toggle dots/error pattern visibility Change-Id: Ie109e82c1fb2fd96b07e977e1cd76ae3acb865ff
* | Merge tag 'android-6.0.0_r26' into HEADRicardo Cerqueira2015-11-051-9/+202
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Android 6.0.0 release 26 Conflicts: cmds/bootanimation/BootAnimation.cpp core/java/android/accounts/AccountManager.java core/java/android/app/AppOpsManager.java core/java/android/os/PowerManagerInternal.java core/java/android/os/storage/IMountService.java core/java/android/provider/Settings.java core/java/com/android/internal/widget/ILockSettings.aidl core/res/res/values-mcc204-mnc12/config.xml core/res/res/values-mcc219-mnc02/config.xml core/res/res/values-mcc730-mnc07/config.xml core/res/res/values/config.xml core/res/res/values/symbols.xml packages/SystemUI/res/values/config.xml packages/SystemUI/src/com/android/systemui/doze/DozeService.java packages/SystemUI/src/com/android/systemui/statusbar/CommandQueue.java packages/SystemUI/src/com/android/systemui/statusbar/ExpandableOutlineView.java packages/SystemUI/src/com/android/systemui/statusbar/phone/DozeParameters.java packages/SystemUI/src/com/android/systemui/statusbar/phone/DozeScrimController.java packages/SystemUI/src/com/android/systemui/statusbar/phone/NavigationBarView.java packages/SystemUI/src/com/android/systemui/statusbar/phone/NotificationPanelView.java packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java packages/SystemUI/src/com/android/systemui/statusbar/phone/StatusBarHeaderView.java packages/SystemUI/src/com/android/systemui/statusbar/phone/StatusBarKeyguardViewManager.java packages/SystemUI/src/com/android/systemui/statusbar/stack/StackScrollAlgorithm.java services/core/java/com/android/server/LocationManagerService.java services/core/java/com/android/server/am/ActivityManagerService.java services/core/java/com/android/server/pm/PackageManagerService.java services/core/java/com/android/server/power/PowerManagerService.java telecomm/java/android/telecom/Phone.java telephony/java/android/telephony/CarrierConfigManager.java telephony/java/android/telephony/RadioAccessFamily.java telephony/java/android/telephony/ServiceState.java telephony/java/android/telephony/SignalStrength.java telephony/java/android/telephony/TelephonyManager.java telephony/java/com/android/ims/ImsCallProfile.java telephony/java/com/android/ims/ImsReasonInfo.java telephony/java/com/android/ims/ImsSuppServiceNotification.aidl telephony/java/com/android/ims/ImsSuppServiceNotification.java telephony/java/com/android/ims/internal/IImsRegistrationListener.aidl telephony/java/com/android/internal/telephony/RILConstants.java Change-Id: I99c6edb8e25a77145b5adef97d0d55bfbe676959
| * Fix jank: Don't write lockout deadline if not neededJorim Jaggi2015-09-281-1/+1
| | | | | | | | | | | | | | | | | | In the longterm, we should move these synchronous writes off the main thread, but in the short term, avoiding an unnecessary write is good enough for the main case. Bug: 24471234 Change-Id: Id996ff29e61410cd077760a06d7868a413ae88da
| * Merge "reset lockout deadline on device reboot" into mnc-dr-devAndres Morales2015-09-161-2/+12
| |\
| | * reset lockout deadline on device rebootAndres Morales2015-09-091-2/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Gatekeeper retains lockouts after reboot, but framework doesn't. This causes odd behavior on a reboot after a lockout as gatekeeper refuses to check the password and the framework thinks it's an invalid attempt. Reset the lockout deadline if we notice the clock reset in the framework. Bug: 23681267 Change-Id: I3127ccd8f205494af5a8ed2b44d4370c37cc2f8f
| * | Revert "Disable fingerprint after force lock"Jorim Jaggi2015-09-101-5/+6
| | | | | | | | | | | | | | | | | | | | | Bug: 23827042 This reverts commit 0cb50efdc2d3ecaa9f1b2163109e8fff1b23f0e7. Change-Id: I40251500b2dcf95e63ce39a768e11a50b26fb923
| * | Don't disable fingerprint when entering wrong credentialAdrian Roos2015-09-031-3/+10
| | | | | | | | | | | | | | | Bug: 23748205 Change-Id: I0ee2a0562d5ef2992a6a4b40d235601b19dcef16
| * | Disable fingerprint after force lockAdrian Roos2015-08-281-7/+6
| | | | | | | | | | | | | | | Bug: 23275072 Change-Id: Icaeffaa1fa22a4a800ddf0f38105099557c74317
| * | Disable fingerprint after user lockoutAdrian Roos2015-08-251-0/+6
| | | | | | | | | | | | | | | Bug: 22677859 Change-Id: I38b918d2e40b5bb423f2e5c171fe65bed8d440a6
| * | Add StrongAuthTrackerAdrian Roos2015-08-211-7/+177
| |/ | | | | | | | | | | Bug: 22846469 Bug: 22115393 Change-Id: I6ef5322d02e540fc043e7f20d3aabf595ce7c224
* | Fix clearing of retained passwordDinesh K Garg2015-10-061-0/+11
|/ | | | | | | | | | | | HW accelerated FDE requires both old and new password to be sent to secure side to verify and update password. This requires storing of old password until password is verified. Initial approach of clearing old password after 60 seconds has a bug which resets old password to default if user delays entering new password. This fix would gives caller the responsibility to clear the password once password is updated. Change-Id: I0ea5cb92ec3908e31c081ce2af6a190c67aadc7b
* [LockSettings] migrate patterns to be indexed at '1'Andres Morales2015-06-021-2/+16
| | | | | | | | | Base zero patterns (ones where the top left is idx 0) are not handled properly by scrypt. Add logic to re-enroll base zero patterns such that the top left is idx 1. Bug: 21433955 Change-Id: I7f67f2c67d40dd1be6c62117710dc3b0392275a2
* Merge "[LockSettings] migrate password attempt throttling to hardware" into ↵Andres Morales2015-05-271-23/+73
|\ | | | | | | mnc-dev
| * [LockSettings] migrate password attempt throttling to hardwareAndres Morales2015-05-261-23/+73
| | | | | | | | | | | | | | | | leverage root protected, cryptographically secured hardware if available Bug: 21118563 Change-Id: Ifa804c5a0728bfd14466eb2a84051bace6d33d57
* | Honor password visible setting in CryptKeeperPaul Lawrence2015-05-181-0/+23
|/ | | | | | Bug: 20184626 Change-Id: Ida0f34299947a5d4067406cc6e029fb841077804
* DOn't save encryption settings when not encryptedPaul Lawrence2015-05-151-2/+5
| | | | | | | | | If this setting is saved when unencrypted, it will apply after encryption and cause the user to get the wrong default in the 'Require pattern to start device' dialog. Bug: 21105662 Change-Id: Ibd2918abb6af27e20dc03a1a10f4cad1033bc575
* Remove LockPatternUtils.getCurrentUser()Adrian Roos2015-04-281-38/+2
| | | | | Bug: 18931518 Change-Id: I177eefe466c12217cf64c85b872f71bc23c7bf05
* Require explicit userId in LockPatternUtilsAdrian Roos2015-04-281-157/+58
| | | | | Bug: 18931518 Change-Id: Ib03f37df9135f0324a998c62d165d8eea46328c8
* Introduced DO_NOT_ASK_CREDENTIALS_ON_BOOT flagAndrei Kapishnikov2015-04-211-5/+10
| | | | | | | | | | | A new flag for DPM.resetPassword() method that specifies that the device should be decrypted without asking for the password or pattern. Bug 19250601 Related CL in Settings App: https://googleplex-android-review.git.corp.google.com/#/c/670206 Change-Id: I9ca3472dc18e66e618ff772dee16ca4a450e9997
* Set REQUIRE_PASSWORD_TO_DECRYPT to false when insecure screen lock isWen ZHANG2015-04-151-0/+2
| | | | | | | | | | | | | | enabled Some users run into a problem when choosing a secure screen lock with accessiblity enabled that they will not be warned the screen lock may not be available when they unlock their devices. One cause is REQUIRE_PASSWORD_TO_DECRYPT is not set back to false when users choose to use an insecure lock screen. So when they decide to change back to a secure screen lock, the warning message will not be shown. Bug: 18799150 Change-Id: I52bdc93e7a5ce3c4f7715057c73b4de280b443f6
* Add challenge to IGateKeeperServiceAndres Morales2015-04-131-0/+36
| | | | | | required for enrolling secondary auth form-factors Change-Id: Id5a1eb1ed22f01fbaabe8e4ebddfc42d58322625
* Wire up GateKeeper to LockSettingsServiceAndres Morales2015-04-131-10/+18
| | | | | | | | | Adds: - Communication to GKService - password upgrade flow - enroll takes previous credential Change-Id: I0161b64642be3d0e34ff4a9e6e3ca8569f2d7c0a
* Allow disabling the lock screen when multiple users are presentBenjamin Franz2015-04-071-17/+17
| | | | | | | | | | | | | Disallowing disabling the lock screen when multiple switchable users are present on the device was a legacy from the time when the lock screen was the only way of switching between users. As we offer other ways to switch users now, e.g. quick settings, we no longer need this check. Also introduce a per user version of disabling the lock screen. Bug: 19962043 Change-Id: I131568a5dadd1706762b8a626e8f9b06e973b7ae
* Merge "Ensure new credentails are valid"Adrian Roos2015-02-051-4/+11
|\
| * Ensure new credentails are validAdrian Roos2015-02-031-4/+11
| | | | | | | | | | | | | | Follow-up to I6f369eb60f8f6bb1e33384cd06534c713ab52e79 Bug: 18931518 Change-Id: I311b255a034b0cec8fee70b0f4938e6ebb20d95e
* | Remove UI code from LockPatternUtilsAdrian Roos2015-02-031-74/+2
|/ | | | | Bug: 18931518 Change-Id: I951166f675731ec7a2bc51585e0a51e0cd92611d
* LockPatternUtils clean up continuedAdrian Roos2015-01-141-236/+165
| | | | | | | | | - Deprecate Settings.Secure.LOCK_PATTERN_ENABLED - Remove unused permanent lock out - Disallow empty/null arguments to saveLockPattern and saveLockPassword - Refactor repeated quality checks Change-Id: I6f369eb60f8f6bb1e33384cd06534c713ab52e79
* Explicitly specify user on LPU's private methodsAdrian Roos2015-01-081-68/+46
| | | | | | | | Also fixes a bug in DevicePolicyManagerService where the wrong user was used. Bug: 18931518 Change-Id: I7ae8ecfdb1c835cdee7eafa2b96e1ec8b712977b
* Directly dispatch USER_REMOVED to LockSettingsServiceAdrian Roos2015-01-071-8/+0
| | | | | Bug: 18931518 Change-Id: Ibaf875a06868ae3196115d77eed6874daf2fec16
* Purge biometric weak and keyguard widgetsAdrian Roos2015-01-071-418/+54
| | | | | Bug: 18931518 Change-Id: I5da41908b1d6895a69f981e139f2d268327fafcd
* am 6d41504d: Merge "Move frameworks users over to libcore hex encoding API."Narayan Kamath2014-12-171-19/+18
|\ | | | | | | | | | | | | automerge: 681e6df1 * commit '681e6df1221ca7671f574d368d428f62184448b0': Move frameworks users over to libcore hex encoding API.
| * Move frameworks users over to libcore hex encoding API.Narayan Kamath2014-12-161-19/+18
| | | | | | | | | | | | | | Removes dependency on apache-http. bug: 18027885 Change-Id: I508db016747985ecdd68e02d5d4efcd0ddd694df
* | Fix DPM.resetPassword("")Adrian Roos2014-11-211-33/+52
| | | | | | | | | | | | | | | | While we're at it, also fix some multi-user issues in LockPatternUtils. Bug: 17496766 Change-Id: I8e557ea640fa589817c8f8f818c91463585d5ea7
* | Update KeyguardManager.isDeviceLocked APIAdrian Roos2014-11-201-12/+47
| | | | | | | | | | Bug: 18414067 Change-Id: I0715714c2c9a122f578ec0c6f508faae12e6f752
* | Obliterate LockPatternUtilsCacheAdrian Roos2014-11-121-12/+1
| | | | | | | | | | | | | | | | It is disabled dead code already and not useful anymore with the new caching in LockSettingsService. Bug: 18163444 Change-Id: Icc184e923e0fbeab31ed128336c01f835b24c6f2
* | Disable LockPatternUtilsCacheAdrian Roos2014-11-101-2/+14
|/ | | | | | | | Also fix a bug where hasPattern and hasPassword were not invalidated properly. Bug: 18163444 Change-Id: I5bd8cc4e7c0d00497ee7a42f3c34449aa3f95a6c
* Add utility methods to LockPatternUtils for encryptionJim Miller2014-10-171-7/+17
| | | | | | | | | This enables a change in Settings that allows device encryption to be disabled by the user. Fixes bug 17881324 Change-Id: I34dfc586df1a598bf969dc82adf8537a2730d345
* Use the correct method to check if device is encryptedAmith Yamasani2014-10-171-4/+1
| | | | | | | | | | | | | DPM's method will return false if encrypted by default password, preventing the changing of encryption password to lockscreen password. Check if the device is encrypted by some means, instead. Also fix a SecurityException when Device Admin queries encryption state (recent regression) Bug: 17881324 Change-Id: Id897e61c5e254ab3f8dc569285428a73005303ea
* Add a checkbox option to 'require password to decrypt'Jim Miller2014-10-141-12/+41
| | | | | | Fixes bug 17881324 Change-Id: Id94e593a172d686339c736473226fece1bb749ee
* Use default encryption password if an accessibility service is enabled.Svetoslav2014-09-301-0/+24
| | | | | | | | | | | | | When device is encrypted the user has to authenticate in order to decrypt the data partition which is required for running accessibility services and Text-To-Speech. In order to address this issue we are falling back to use the default password if there is an enabled accessibility service and the user has secure lock. This will enable the user to authenticate when accessibility layer is completely functional. bug:17671790 Change-Id: Iafffe7bcd234008cf91ffb5011b21b803dca227a
* Set the system locale correctly even on an encrypted device.Elliott Hughes2014-09-261-2/+2
| | | | | Bug: 17659622 Change-Id: Ibbbd5b959bfab5345f20b556c4720d0910b50084
generated by cgit v1.1 at 2024-05-20 08:32:45 +0000