- Oct 25, 2023
-
-
Eric Biggers authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2796606 Change-Id: If5917603823cf1fae25ba246015f566fbac91182 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Eric Biggers authored
-
Eghosa Ewansiha-Vlachavas authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2801133 Change-Id: I5fdded0dce526a6b5cf849571d4253dc88ed9d8c Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Eghosa Ewansiha-Vlachavas authored
-
Song Chun Fan authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2803437 Change-Id: I3294991be1d25d54a5ed328766a6c17bc62ae7d8 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Eric Biggers authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2796609 Change-Id: I46bd16fb681fa860ef4a4aed35cf8ea265c704c5 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Song Chun Fan authored
-
Eric Biggers authored
* changes: Use isCeStorageUnlocked() in StrictMode.java Rename methods for creating and destroying user's storage keys Rename methods for unlocking, locking, and protecting CE storage
-
Prabir Pradhan authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2802455 Change-Id: I301217bbf02f7bd3acd4c35b0be016b3411807ba Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Prabir Pradhan authored
-
Munikrishna J authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2795876 Change-Id: Icf3b978b65d6e6d490fa58f3873a81d0d71aad14 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Munikrishna J authored
-
Anton Hansson authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2796122 Change-Id: I0fed9b5fcecccc38b00b20b661ebe683d1d824ea Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Anton Hansson authored
-
Kangping Dong authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2801853 Change-Id: I5ffb98b69d2d89e42a215ea339c6372a3d347f89 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Kangping Dong authored
-
Kangping Dong authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2801273 Change-Id: If1a050b63f8dec97d9c5485a5fe2bcf638fc0400 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Kangping Dong authored
-
- Oct 24, 2023
-
-
Eric Biggers authored
Document more clearly what unlockUserKeyIfUnsecured() actually does. It probably should be renamed to something clearer (I'm thinking of just changing "Key" to "Keys"), but this is a start. Bug: 306204742 Flag: exempt, comment-only change Test: presubmit Change-Id: Ib35a62fb4627db5755fac57609b1fbb3a659492d
-
Eric Biggers authored
isUserKeyUnlocked() is being renamed to isCeStorageUnlocked() to make it clear what it does (considering that there are many types of user keys). Change StrictMode.java to use the new name. No change in behavior. Bug: 306204742 Flag: exempt, mechanical refactoring Test: presubmit Change-Id: I4616b55cc4a088cfd396cc1b4ad60f3ecfed942b
-
Eric Biggers authored
Users have many cryptographic keys, such as: - Storage (file-based encryption) keys, both CE and DE - Keystore super keys, both AfterFirstUnlock and UnlockedDeviceRequired - Keystore client keys - Synthetic password and the Keystore key that encrypts it Unfortunately, many StorageManager, vold, and LockSettingsService methods refer simply to "UserKey". It isn't clear or consistent which key(s) they mean. For example, unlockUserKey unlocks CE storage, createUserKey creates both the CE and DE keys, and unlockUserKeyIfUnsecured unlocks CE storage but also does other things. With the planned fixes to handle Keystore super keys more similarly to the CE storage key (b/296464083), this confusion will increase further. This CL is the second part of fixing this. It renames the following methods of StorageManager to make it clearer what they do: createUserKey => createUserStorageKeys destroyUserKey => destroyUserStorageKeys No change in behavior, except a changed trace tag name and log message. Bug: 306204742 Flag: exempt, mechanical refactoring Test: presubmit Change-Id: I5894beb97823dced5954e405d779fada49c79e8d
-
Eric Biggers authored
Users have many cryptographic keys, such as: - Storage (file-based encryption) keys, both CE and DE - Keystore super keys, both AfterFirstUnlock and UnlockedDeviceRequired - Keystore client keys - Synthetic password and the Keystore key that encrypts it Unfortunately, many StorageManager, vold, and LockSettingsService methods refer simply to "UserKey". It isn't clear or consistent which key(s) they mean. For example, unlockUserKey unlocks CE storage, createUserKey creates both the CE and DE keys, and unlockUserKeyIfUnsecured unlocks CE storage but also does other things. With the planned fixes to handle Keystore super keys more similarly to the CE storage key (b/296464083), this confusion will increase further. This CL is the first part of fixing this. It renames the following StorageManager methods to make it clear that they deal with CE storage: unlockUserKey => unlockCeStorage lockUserKey => lockCeStorage setUserKeyProtection => setCeStorageProtection In addition, it starts the renaming of: isUserKeyUnlocked => isCeStorageUnlocked However, isUserKeyUnlocked is used more widely and is also a @TestApi, so for now it still exists alongside the new name. Later CLs will convert the remaining callers of isUserKeyUnlocked to use the new name. No change in behavior except for some changed log messages. Bug: 306204742 Flag: exempt, mechanical refactoring Test: presubmit Change-Id: I202ebbfd2b4f79fedb3ed120a8ad81500c126894
-
Prabir Pradhan authored
... until we figure out a way to determine if a device supports a specific HID usage code. Right now, having a usage code mapping means we automatically assume the device can report the key code. Assuming a device can support a stylus keycode makes the device get classified as a stylus, leading to widespread misclassifications. Bug: 291529805 Test: atest inputflinger_tests (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:5fb192aaec7a1d4ebb1384d96b3f79d4b2ca2f2c) (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:55930e07d69fbd8ffd27d677a06fd0ba71a30bf8) Merged-In: I580514bdcbbfbe93df83fa3faa6262077e881243 Change-Id: I580514bdcbbfbe93df83fa3faa6262077e881243
-
Treehugger Robot authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2799541 Change-Id: I9c26d1942f56cd49be425c7d1dbb2df47e5afe24 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Treehugger Robot authored
-
Kangping Dong authored
Bug: 304478648 Test: build Change-Id: I4c102131c9f1639d894b95114c76028808b64c2f
-
David Duarte authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2787579 Change-Id: Idc38551b74aa2fd69f5e75107eefb27e9ba50954 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Anton Hansson authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2799993 Change-Id: I2dbcf61171ff94a7a5fa91bf6b1c285240e9a394 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
David Duarte authored
-
Anton Hansson authored
-
Roshan Pius authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2799364 Change-Id: I2696a4f6a08cdc960f09ec937d9dabead69ed4bd Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Roshan Pius authored
-
Anton Hansson authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2799416 Change-Id: Iac6fee1d6794fb55015c4b04bac808d6ca1ef8be Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Anton Hansson authored
-
Anton Hansson authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2799733 Change-Id: I1fdf0b565253281352fe3ad41bee2162db88081c Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Anton Hansson authored
-
Kangping Dong authored
This commit annotates the PackageManager#FEATURE_THREAD_NETWORK API with the "com.android.net.thread.flags.thread_enabled" flag. Bug: 303726779 Test: build Change-Id: I09a27a71b2beab7902bf29b44fb9c36cc3ce2f20
-
Nathalie Le Clair authored
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/2796408 Change-Id: I44a039efd40629a3eb57661ea520d8da15a55d83 Signed-off-by:
Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
-
Nathalie Le Clair authored
-
Eghosa Ewansiha-Vlachavas authored
Bug: 290589995 Test: n/a Change-Id: I7f41eabfd568bae441d1d4fb75f36c4dc58bab60
-