| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: Ife51e0b742f8fc1809ac53d676d3644b06cd8789
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: Ie9641c36b244cf85d9a5d17b2185f7c26d1b4ec3
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I27c8c543212829794bec781cb543af3d7169ca7f
Auto-generated-cl: translation import
|
|
|
|
|
|
|
|
|
|
|
|
| |
New behavior. Backup no longer uses the encryption password. This is in
part because that is hard with patterns, in part because it is a security
issue - the off line backup is much easier to brute force than the phone.
Instead, we simply insist on an encryption password if your device is encrypted
and locked.
Bug: 17159330
Change-Id: Ia22f84722522abf0b569a3ef1e16ead5527c726d
|
|
|
|
|
| |
Change-Id: I331a48ef418aa24e80bf690a566dd970e7a2b398
Auto-generated-cl: translation import
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Iac5489639edae2373ed0ce92f7d0fe22629a249a
|
|/
|
|
|
| |
Change-Id: Iccd6de29591b724ac87fbd83638f5eb256daceb1
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I87bdb10cbf1f6ad9f0561ef07e99378e1863fca8
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: Ie5bf42a8ca0f627fe2f0b3c041ab7cabdef9edfb
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I22e8f15798ef15540c370bb14eea6cf9af6ae43c
Auto-generated-cl: translation import
|
|\
| |
| |
| |
| | |
* commit 'e3c38a0b0ebefa0a86be944259467c8acc9e5e49':
Fix recents theme, add missing headers
|
| |
| |
| |
| | |
Change-Id: Ib8eea6153eaf7e0e93e54c69fe59e63e98a409a6
|
| |
| |
| |
| |
| | |
Change-Id: I11f3f5a70625de845a8afcbffef04e274a8a73c9
Auto-generated-cl: translation import
|
| |
| |
| |
| |
| | |
Change-Id: I735b0a0de031b145b54b9cf643b7e91bb40c426d
Auto-generated-cl: translation import
|
|/
|
|
|
| |
Change-Id: I7aef0ba2b5f45b3e60d7840408176c6a61d9d8ee
Auto-generated-cl: translation import
|
|
|
|
|
| |
Bug:11340849
Change-Id: Ib99486303927a6bce308b113d70f8e5b5bce4a13
|
|
|
|
|
| |
Change-Id: Ib85aee9822ee5258fb7ad1b2d8e7c65c71991803
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I2dfe3d6bca7948bce139f0f0f1404214ad8c99f2
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: Ieb610ced7d3f541bc238646988904ed1cb7cee7a
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I2d9b9480f24eed9e6ec962222d212bbfb1179cde
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I58312f6de5060de6fdf5815a304c3ba502b717ce
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: Ib755452de5a0757b20e644634a0cfbec59cdf235
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I400da658acf872787f81dc223a4c3cf40ceb2f50
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I3560b16b347b71c61ad1f723d444dbd056ee0d8f
Auto-generated-cl: translation import
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"signatureOrSystem" permissions are no longer available to all apps
residing en the /system partition. Instead, there is a new /system/priv-app
directory, and only apps whose APKs are in that directory are allowed
to use signatureOrSystem permissions without sharing the platform cert.
This will reduce the surface area for possible exploits of system-
bundled applications to try to gain access to permission-guarded
operations.
The ApplicationInfo.FLAG_SYSTEM flag continues to mean what it is
says in the documentation: it indicates that the application apk was
bundled on the /system partition. A new hidden flag FLAG_PRIVILEGED
has been introduced that reflects the actual right to access these
permissions.
At some point the "system" permission category will be
renamed to "privileged".
Bug 8765951
Change-Id: I6f0fd9cdb9170e076dfc66d83ecea76f8dd7335d
|
|
|
|
|
| |
Change-Id: I6ac969ffc6fbffeb262ec79b14a4155f2123d82d
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: Ie31e6632a217b9b9c7c0ebb79b16747830370db1
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I830962076909bd65156b0e56bc8b9a4f44b7b249
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I2f901cb989904c4325c2064428e4b8b0b2225d06
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: Ied34352ea4e79b01a9b8549596a381fe08ee7e06
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I8b0d4f8146956bb0569ec01ef0872ad0a7065f0c
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I819f42df4c6909d695e78420670d76919a497c06
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I37cdf72141038d6677c0ffe3f1ef6f65bf6fd78a
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: I4036c81a0a932e366969e9e333bbe3c5d46a9cd8
Auto-generated-cl: translation import
|
|
|
|
|
| |
Change-Id: Iabb056f645a910f3fbaea1e51348c3bef385546e
Auto-generated-cl: translation import
|
|
|
|
|
|
|
|
|
|
|
| |
The confirmation UI did not request the needed permission, so was failing
to communicate with the mount service; as a "safe" failure mode, it was
assuming the device was encrypted. Fixed; now it presents the correct
prompt text for the device's encryption state.
Bug 5958195
Change-Id: Ic03db16673b89d3377e0362a09cf51bfb572d78b
|
|
|
|
| |
Change-Id: Ie43246df49b8f6ef3daef12e0d8fb5c2f573874e
|
|
|
|
| |
Change-Id: I71efb16f2c6b257dfd444728c7e56ada662e6f77
|
|
|
|
| |
Change-Id: I5db0a5df334833af2e2109123d05a9f76c745cf6
|
|
|
|
| |
Change-Id: I83ab00ec220b7c0ba0d37e7f4c91e945e35aab39
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This supersedes any backup-password that the user might supply. Per
design, the device encryption password is also always used to encrypt
the backup archive.
The CL introduces two new strings, used for prompting the user for
their device encryption password rather than their settings-defined
"backup password" when confirming a full backup or restore operation.
Bug 5382487
Change-Id: I0b03881b45437c944eaf636b6209278e1bba7a9f
|
|
|
|
| |
Change-Id: Id046f8008aef32a1b94b4fa5b57e2beb2f9f2e80
|
|
|
|
| |
Change-Id: Ic8e228878fde375b90797c6e344fcb3114180f1d
|
|
|
|
| |
Change-Id: I5e375bebc8f74d9108a929246f16608427ce9317
|
|
|
|
|
|
| |
...in the full backup/restore confirmation UI.
Change-Id: I858a2d7017450f016afe5052aa37161a1c89c281
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the confirmation uses the same Activity but different layouts
for the backup vs restore cases, we have to do the title in code.
Along the way, fix the restore layout's padding [the backup layout
was already right].
Fixes bug 5164470
Change-Id: I4d636f666d97fc377e9cf36abf08d1625a05577f
|
|
|
|
| |
Change-Id: I6e7f33ff16557f7e9088c0aa66fd1c79ed376c75
|
|
|
|
| |
Change-Id: Iac73006cfaf846d210855496f6732cbdc6ad0de8
|
|
|
|
| |
Change-Id: I51e1fc94b7fa3fec13f7dddad62b978dd9a71d43
|