summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Hide overlays over WifiInstaller dialog" into rvc-qpr-dev am: e1f0cc8afbtemp_ab_7272582Rubin Xu2021-03-311-1/+6
|\ | | | | | | | | | | Original change: https://googleplex-android-review.googlesource.com/c/platform/packages/apps/CertInstaller/+/13918846 Change-Id: Ib3a9b55d5fe5170c357b6c97e4efb46cc03d01e8
| * Hide overlays over WifiInstaller dialogRubin Xu2021-03-181-1/+6
| | | | | | | | | | | | | | | | Bug: 176756141 Test: manual Merged-In: Ib4e11c573ddfc782a5068440c4d6ee48378be511 Change-Id: Ib4e11c573ddfc782a5068440c4d6ee48378be511 (cherry picked from commit 0aead2d61a342da96cf51e72774c691dee42719f)
* | [WifiInstaller] Delete files only if parsed successfully am: 2e6f670e6fHai Shalom2021-03-051-22/+47
|\| | | | | | | | | | | | | | | Original change: https://googleplex-android-review.googlesource.com/c/platform/packages/apps/CertInstaller/+/13681584 MUST ONLY BE SUBMITTED BY AUTOMERGER Change-Id: I26aff4d941a46b162ca2174dddd1207525914272
| * [WifiInstaller] Delete files only if parsed successfullyHai Shalom2021-02-251-22/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added input checks and delete the configuration file (passed as a URI) only if it contains a valid Passpoint configuration. Bug: 176756691 Test: Download a real configuration file, verify correct installation and file deleted. Test: Download a garbage file with the correct mime type, verify that installation fails and the file is not deleted. Change-Id: Ic9106d46abd9bed642465b8d023bac6dfc5a0f3b (cherry picked from commit 834fe82d8926a3e1ba1ce2a0811f921f006190da) Merged-In: Ic9106d46abd9bed642465b8d023bac6dfc5a0f3b
| * Update CertInstaller message to include app name.Pavel Grafov2020-06-192-1/+28
| | | | | | | | | | | | Bug: 159324357 Test: local with CtsVerifier Change-Id: I5a0103bcd652908080148e5dd3752aa453b6369c
| * Merge "Prevent guest user from installing credentials" into rvc-devTreeHugger Robot2020-05-141-1/+2
| |\
| | * Prevent guest user from installing credentialsRubin Xu2020-05-131-1/+2
| | | | | | | | | | | | | | | | | | Bug: 123343103 Test: creat guest user, downlaod p12 file and try to launch it. Change-Id: I7d692607164fa7a801e3932e691375bb6dde9ad7
| * | [WifiInstaller] Remove Passpoint profile before installingHai Shalom2020-05-131-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Due to a change in the addOrUpdatePasspointProfile behavior, Wi-Fi cert installer needs to delete existing Passpoint profile before installing a new one with the same FQDN. Bug: 156405566 Test: Install a new cert, verify correctness. Change-Id: Ib258750f546f81cdf1081bbff5c0f1c4c23fd070
| * | Install WiFi certificate from Files appAlex Johnston2020-05-072-11/+6
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Certificate usage dialog is shown when a certificate is selected from the Files app. * If the radio button WiFi is selected, then the UID needs to be set to the WIFI_UID. Manual testing steps * Add WiFi certificate to device * Go to Files and select the certificate * Select WiFi radio button in certificate usage dialog * Name the WiFi certificate * Go to Settings > Security & Credentials > User Certificates and verify installed certificate is a WiFi certificate and not a VPN & Apps certificate. Bug: 155783269 Test: manual testing Change-Id: I6bf8cd8d2ca60894e4b4bdc3b4573b5bc21163f2
| * Modify name certificate dialogAlex Johnston2020-04-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Context * Talkback does not announce dialog title when name certificate dialog is shown. Changes * Remove TextView for title from name_certificate_dialog.xml * Add dialog.setTitle() instead Bug: 152456397 Test: manual testing Manual Testing Steps - Add a certificate to device - Go to Settings > Security > Encryption & Credentials > Install a certificate > VPN & app user certificate - Select certificate and verify dialog title is displayed correctly Change-Id: I76950aa5ccf28de7553a554a48332e15861b16f7
| * Revert "Handle the new app source certificate"Victor Hsieh2020-02-143-61/+19
| | | | | | | | | | | | | | | | | | | | We decided to punt extra certificate to post-R. This reverts commit bc20afad71aae40109862a395c96b3ac18aed7de. Test: Treehugger Bug: 112038744 Change-Id: I4300e84a8d73b446cfdf1a18ecd3c5f9b2787aeb
| * Updated WiFi certificate flowAlex Johnston2020-01-142-31/+20
| | | | | | | | | | | | | | | | | | | | | | * Updated WiFi certificates to show the name dialog (this dialog is already shown for user certificates). * Updated logic to allow a CA certificate to be selected as a WiFi certificate. Bug: 147473033 Test: manual testing Change-Id: Ia0be378c13e2ac1a5623fa084e1fad10d862696f
| * KeyChain: Do not allow hiding Cert Install dialog am: afdacb2ec4 am: ↵Automerger Merge Worker2019-12-041-0/+3
| |\ | | | | | | | | | | | | | | | 2151a76f90 am: 83b9e9fa5c am: 734d1c1143 Change-Id: I6c9303a1cf6e178f2e8c65e32aaad508227714bf
| * | Handle the new app source certificateVictor Hsieh2019-11-253-20/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new cert type - needs user authorization to install (same as CA cert) - does not need a name from user (same as CA cert) - needs to be install to keystore under its own uid (same as WiFi cert) - needs a reboot to be effective since it's loaded to kernel at boot - is only actually used when enabled on the device (not required yet) Test: install from Settings, see the file stored in /data/misc/keystore/user_0 Build: 112038744 Change-Id: I56d2418069435c366f17cf346e5d1e47ba758a91
| * | Added invalid certificate dialogAlex Johnston2019-10-291-2/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is part of the changes to improve the UX and language for installing certificates. With the addition of the Settings page to select the type of certificate to install, additional logic is required to ensure an appropriate certificate is selected. This CL does validation checks and will show a dialog if the wrong certificate type is selected. Bug: 139173976 Test: manual testing by selecting different certificate types with the file picker Including testing certificate which needs to be extracted go/enterprise-wifi-lab-access Screenshot of the screen: https://hsv.googleplex.com/4890125932691456 Change-Id: I45064f7b5a14d84232d7009fa7c2b1387f674ae4
| * | Created dialogs when installing certificates outside SettingsAlex Johnston2019-10-293-16/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is part of the changes to improve the UX and language for installing certificates. Previously, all certificate types could be installed from the Settings app and other apps. This CL prevents CA certificates from being installed outside of the Settings app. It also introduces new dialogs: - CA certificate: dialog to redirect user to Settings - User/WiFi certificate: dialog to select certificate usage and enter certificate name Bug: 139173976 Test: manual testing by installing different certificate types from the Files app Including testing certificate which needs to be extracted go/enterprise-wifi-lab-access Screenshot of the screen: https://hsv.googleplex.com/5073669078384640 https://hsv.googleplex.com/5697514017652736 Change-Id: I1a456ef9d8f139345b6159e1ad83d2d3a14687f8
| * | Separated flow when installing different certificate typesAlex Johnston2019-10-253-78/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is part of the changes to improve the UX and language for installing certificates. Previously when installing a certificate, the same dialog appeared for all certificates. This CL introduces a separate flow for the different types: - CA certificate: confirm credential, select certificate, install - User certificate: select certificate, name dialog, install to keystore - WiFi certificate: select certificate, install to keystore Bug: 139173976 Test: manual testing by installing different certificate types: CA, User and WiFi Including testing certificate which needs to be extracted go/enterprise-wifi-lab-access Screenshot of the screen: https://hsv.googleplex.com/5666804900823040 Change-Id: I9b24c37b382eeecee6e5d0d74cbd4047c6d36182
| * | Confirm credential after warning dialog when installing CA certificateAlex Johnston2019-10-242-34/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is part of the changes to improve the UX and language for installing certificates. Previously, confirm credentials occurs once a CA certificate is selected from the file picker. This CL moves the confirm credential logic to appear after the warning dialog and before the file picker, when installing CA certificates. Bug: 139173976 Test: manual testing from Settings by selecting the certificate type preference and ensuring the installation flow still worked as expected. Change-Id: Iba737f391fa672a305daae475467d5d25a6206df
| * | Added functionality to select type of certificate to be installed from the ↵Alex Johnston2019-10-181-22/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Settings app This is part of the changes to improve the UX and language for installing certificates. Previously, the different types of certificate used the same installation flow. This CL introduces a new settings page, where the type of certificate to be installed can be selected. Bug: 139173976 Test: Atest com.android.settings.security manual testing from Settings by selecting the new certificate type preference and ensuring the installation flow still worked as expected. Change-Id: I48a35183cfe08e236c98f7a2b5ad498edc6d5d56
| * | Merge "Unify manual and programmatic key installation flows"Eran Messeri2019-09-182-14/+12
| |\ \
| | * | Unify manual and programmatic key installation flowsEran Messeri2019-09-122-14/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is part of the work to unify the manual certificate installation flow (via "Install from storage" in the Settings app) with the programmatic one (using DevicePolicyManager.installKeyPair). The CertInstaller is changed as follows: * Installation of CA certificates no longer invokes the Keystore installation flow. Previously, CA certificates installed manually ended up with an entry created in Keystore, which was completely pointless (and confusing). Instead, it happens after the "name credentials" dialog, once the user has assigned a name for the credential, and is mutually exclusive of installation of user key. * Rather than passing the individual Keystore names for the user key, user certificate and associated certificate chain, only the user-assigned name is passed as an extra to the installation intent. To do at a future date: Break down the dialog for CA certificate installation from that of a user credentials naming. First, there's no need to "name" a CA certificate. Second, a different, and scary, warning should be shown for that case. Test: Manual CtsVerifier tests: KeyChain Storage Test, CA Cert Notification Test Test: cts-tradefed run commandAndExit cts-dev -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement Bug: 138375478 Change-Id: I2ae5bf2ac3b21a0c4c44ad290e3f65c88cb5213c
| * | | Remove config_auto_cert_approval from CertInstallerAlex Johnston2019-08-301-5/+1
| |/ / | | | | | | | | | | | | | | | | | | Bug: 134127620 Test: manual build Change-Id: Ia29e27a052b0844ca16b572ef5aa33209076cbfe
| * | Move install component into config file.davidln2019-06-202-4/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will allow for specifying the location of credential storage in a resource overlay. The specific use case is for automotive builds in which com.android.settings is replaced by com.android.car.settings. Bug: 130199964 Test: -m cts-verifier -adb install -g out/<path to apk>/CtsVerifier.apk -adb shell setprop log.tag.KeyChainTest DEBUG -Launch CTS Verifier from app launcher -Scroll to "KeyChain Storage Test" in Security section -Tap to begin test and follow prompts on screen -Accept dialog prompt to install certificates -Ensure toast is shown that certificates installed successfully -Complete test steps and verify in logs that "Connection succeeded" Change-Id: I77e69e934084059130b3b217992ef508e1c5f55c
* | | CertInstaller: use unbundled version of BouncyCastle. BouncyCastle APIs ↵Daulet Zhanguzin2021-01-271-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | cannot be exposed in updatable ART. Bug: 154796679 Test: Treehugger Test: atest CertInstallerRoboTests Change-Id: I81b43f7dd7b04d20a434ea80867b09c2cecf1eca
* | | Merge "Update language to comply with Android's inclusive language guidance"Treehugger Robot2020-08-031-1/+1
|\ \ \
| * | | Update language to comply with Android's inclusive language guidanceChiachang Wang2020-08-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | See https://source.android.com/setup/contribute/respectful-code for reference. Bug: 161896447 Test: m Change-Id: Ideeb63461656f886d78225e5b5c66ad17a04ef14
* | | | Refactor CredentialHelper ConstructorJudith Offenberg2020-07-232-25/+63
|/ / / | | | | | | | | | | | | | | | | | | | | | Move Intent parsing logic to caller function Bug: 143515180 Test: atest CertInstallerRoboTests Change-Id: Ie04a8b21c56a10e52468304528ebfb22605d4756
* | / [DO NOT MERGE] Rollup changes from RAlex Johnston2020-07-154-151/+357
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change includes the following commits from internal R branch: 7a7578a Remove config_auto_cert_approval from CertInstaller 313c05a Unify manual and programmatic key installation flows 91a7c21 Added functionality to select type of certificate to be installed from the Settings app 2e6c20e Confirm credential after warning dialog when installing CA certificate ffac486 Separated flow when installing different certificate types 2138394 Created dialogs when installing certificates outside Settings d5aa3c3 Added invalid certificate dialog adecd13 Updated WiFi certificate flow 5d14580 Add an exported flag in manifest 10d9c4f Fix strings for certificate installation in CertInstaller 8df978d Modify name certificate dialog 9cdfff2 Install WiFi certificate from Files app c43d233 [WifiInstaller] Remove Passpoint profile before installing 2411689 Prevent guest user from installing credentials a9ec06a Update CertInstaller message to include app name. Bug: 161347472 Test: builds & manual testing Change-Id: I01a48a7d91c40a83db1f21b29c0d8df2724604c7
* | KeyChain: Do not allow hiding Cert Install dialog am: afdacb2ec4 am: 2151a76f90Automerger Merge Worker2019-12-041-0/+3
|\ \ | | | | | | | | | Change-Id: I884baaf530f8b19a8e742334ad9eb74078a649c5
| * | KeyChain: Do not allow hiding Cert Install dialogEran Messeri2019-11-061-0/+3
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Do not allow apps to float a window on top of the certificate installation / naming dialog. This obscures the CA certificate installation dialog and could be used to trick a user into installing a CA certificate. This is fixed by adding the HIDE_NON_SYSTEM_OVERLAY_WINDOWS system flag when the activity is created (onCreate), so that another activity starting in the foreground would not be able to obscure the dialog. Bug: 139017101 Test: Manual, with an app that floats a window. Change-Id: Iff8e678743c3883cf1f7f64390097a768ca00856
* / Move install component into config file.davidln2019-09-042-4/+3
|/ | | | | | | | | | | | | | | | | | | | | | | This will allow for specifying the location of credential storage in a resource overlay. The specific use case is for automotive builds in which com.android.settings is replaced by com.android.car.settings. Bug: 130199964 Bug: 139705828 Test: -m cts-verifier -adb install -g out/<path to apk>/CtsVerifier.apk -adb shell setprop log.tag.KeyChainTest DEBUG -Launch CTS Verifier from app launcher -Scroll to "KeyChain Storage Test" in Security section -Tap to begin test and follow prompts on screen -Accept dialog prompt to install certificates -Ensure toast is shown that certificates installed successfully -Complete test steps and verify in logs that "Connection succeeded" Change-Id: I77e69e934084059130b3b217992ef508e1c5f55c Merged-In: I77e69e934084059130b3b217992ef508e1c5f55c (cherry picked from commit 0045d56af4395ab26a30aa528ebfeadfec025e5d)
* Confirm user credentials _only_ for CA certificateEran Messeri2019-06-051-2/+7
| | | | | | | | | | | | | | | | | | Confirm the user's credentials only if a CA certificate is installed, not if a user certificate + public key is installed. Change Ib998a2fcdff6ceaac515e99245fd5fe3bf202d5a introduced a regression where the users credentials are confirmed if CredentialHelper.hasCaCerts() returns true. However the "CA certificates" in the credentials helper has multiple uses - in case a client certificate chain is installed it will contain the certificates that are not the leaf client certificate. It does not make sense to confirm credentials in this case. Bug: 134057817 Test: Manual Change-Id: I5e5de99808be5bc72bf6b3f25860d8ce8df9cd32
* Confirm user credentials before installing CA.Pavel Grafov2019-05-302-106/+89
| | | | | | | | | | | | In addition only approve CA cert when the user has a lockscreen so that it is impossible to install a CA cert without the user being notified. + trivial clean up and simplification. Bug: 130622999 Test: manual via CtsVerifier Change-Id: Ib998a2fcdff6ceaac515e99245fd5fe3bf202d5a
* Fix key algorithm serializationEran Messeri2019-03-071-5/+12
| | | | | | | | | | The CredentialHelper assumed that the key algorithm for the private key imported was always RSA. Fix that incorrect assumption by saving the user key algorithm. Bug: 127385358 Test: Manual, install EC key. Change-Id: I3e1e1e7249f78f15a38d80584f7f969acdc2de24
* Fix manual CA certificate installation flowEran Messeri2019-02-061-2/+11
| | | | | | | | | | | | | | | Manual CA certificate installation broke because a precondition check in the CertInstaller only expected to name the credentials if they were user credentials. Fix this by allowing naming of a CA certificate, thus fixing a regression in Q. Bug: 122583145 Bug: 118689131 Bug: 123636017 Test: Manual, installed a CA certificates via the Settings -> Security -> Encryption & Credentials -> Install from storage Change-Id: Ic25f5b382c133ac3a60e3f1b4be852e712a524d8
* Remove Wear special-case handlingEran Messeri2019-01-241-11/+2
| | | | | | | | | | | | | Since Wear's version of CredentialStorage is no longer going to be used, remove the code in the CredentialHelper that sends an intent directly to it. Additionally, since the CredentialStorage class is moved, point to its new package. Bug: 120901345 Test: Manual with TestDPC, CtsVerifier Change-Id: I7844b4d787b101b2e652cf7d2545d75bec488a98
* KeyChain: Remove screenlock requirementEran Messeri2019-01-171-49/+24
| | | | | | | | | | | | | In coordination with KeyChain changes, stop using FLAG_ENCRYPTED when importing keys into KeyStore and remove the requirement that a screen lock is present. See the KeyChain change for more details. Test: atest CtsDevicePolicyManagerTestCases:com.android.cts.devicepolicy.MixedProfileOwnerTest#testKeyManagement Bug: 120901345 Change-Id: I61805dd128b4c9b8dc59e8bdda3343dd052c863d
* Install a certificate together with a private keyEran Messeri2018-05-022-57/+15
| | | | | | | | | | | | | | | | | | | | | | | The CertInstaller supported a feature where a user certificate can be installed in two steps: (1) An intent is received with the private&public key pair, the private key is saved. (2) An intent is received with the user certificate, the private key associated with it is loaded and saved with the certificate. The problem with this flow is that user authentication happens only on the 2nd phase, allowing an attacker to mess with the keys saved in (1), potentially disrupting certificate installation flow. CertInstaller should not be in the business of storing intermediate client data. Require that the intent sent to install a user certificate contains both the user certificate and the associated private key. This is less error prone and prevents an attacker from changing internal CertInstaller state without user authentication. Bug: 65543118 Test: Manual (see PoC in the bug). Change-Id: Ie17505c70adf0c1af748c5aae42b9ba7102aba72
* Inform the user about the implications of installing a CA certificateEran Messeri2018-03-211-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | Tell users that installing a CA certificate potentially allows the issuer of said CA certificate to intercept all traffic to the device. Broadly, users that install a CA certificate via the settings menu should understand what the certificate is capable of doing. However, apps can trigger the intent for installing a CA certificate and may trick an unsuspecting user into installing a CA certificate without telling the user what that implies. Notify the user that the CA certificate can be used for intercepting traffic if it's installed for 'VPN and apps' (a system CA). It should be noted that since N, Android apps no longer trust locally-installed CA certificates by default. However, many apps (such as Chrome) intentionally opt-in to trusting such certificates. See https://android-developers.googleblog.com/2016/07/changes-to-trusted-certificate.html for more context. Bug: 73757661 Test: Manually Change-Id: Ibbd28faad763ba29651d4ed3b00caead3d7ad18f
* Merge "Limit cert file reading to 10MiB." am: ae1a16bd41 am: 3500e1ce00Adam Vartanian2018-02-271-3/+29
|\ | | | | | | | | | | am: 451eb26688 Change-Id: Ibf5ca6147628f6bcdba0e1c1305b5113679997e8
| * Limit cert file reading to 10MiB.Adam Vartanian2018-02-261-3/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | We read the entire cert file into memory when installing it, so reading without a limit will cause OutOfMemoryErrors if the file is sufficiently large. This is not a security problem (if someone can trick the user into installing new certificates, crashing the cert installer dialog is by far the least impactful thing they could do), but it's nice to not crash. Bug: 32320490 Test: manual testing Change-Id: Ib8dbfe06304481fd682297c680841705b8c4ad7c
* | WiFiInstaller: catch exceptions on both delete paths am: 881958d4b9mukesh agrawal2017-10-151-6/+6
|\| | | | | | | | | | | am: f3ba2e7812 Change-Id: Id0043d9ffb740b8dbe27779712fec7ceace94c11
| * WiFiInstaller: catch exceptions on both delete pathsoreo-mr1-devmukesh agrawal2017-10-121-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | WiFiInstaller provides the ability to automatically install a Passpoint configuration, if that configuration is served using the 'application/x-wifi-config' MIME type. Before installing the configuration, WiFiInstaller reads the configuration data into memory, and then attempts to delete the file. If the file was provided using the DocumentsContract API, then a failure to delete will be caught and logged. The installation of the configuration can still succeed. If, however, the file was provided using a ContentResolver, then a deletion failure causes the install process to fail. When Chrome is used to download a Passpoint configuration from a Passpoint provider, we see that the install reliably fails. The failure occurs because the config file is a) not provided using a DocumentsContract, and b) can not be deleted. To resolve the failure, we handle a failure to delete a ContentResovler-provided config the same way that we handle a failure to delete a DocumentsContract-provided config. Namely: catch the exception, log the failure, and continue to install the config. We will work separately to determine why this problem is only now surfacing. (We suspect some change in the way that Chrome provides the file to WiFiInstaller.) BUG: 66971720 Test: manual Manual test ----------- 1. flash build with changes onto device 2. open passpoint.boingo.com in chrome 3. scroll to bottom of page 4. tap 'Create Profile' 5. enter username and password from bug 6. tap 'Download Profile' 7. see 'Chrome needs storage access...' prompt 8. tap 'CONTINUE' 9. see 'Allow Chrome...' prompt 10. tap 'ALLOW' 11. see 'Install Wi-Fi credentials' prompt 12. tap 'INSTALL' 13. see 'Credentials installed' dialog 14. adb logcat -d | grep 'could not delete' 10-12 17:23:23.759 17030 17030 E WifiInstaller: could not delete document content://com.android.chrome.FileProvider/downloads/BoingoPasspointProfile (last step confirms that this patch was necessary) Change-Id: I5cc4ac9cec8d6942f64ede696ccac3a6d9204922
* | Add config to switch auto-approval for user certDaichi Hirono2017-08-011-2/+7
|/ | | | | | | | | | If a device does not have the lock screen, the auto-approval feature needs to be disabled to pass CTS verifier tests, because there is no way to show the cert notification after auto-approved. Bug: 34111731, 62387735 Test: Ca Cert Notification Test Change-Id: I55a0afc9573e1762547bb2a264fa01c5ffc2e077
* Fix crash in CertInstallerRubin Xu2017-04-242-1/+2
| | | | | | | | Create dialog view before accessing its subview. Bug: 37295281 Test: Manually install malformed pkcs12 files from the bug above. Change-Id: I3a8eb039707b4ea8a1ce6c7cafe4eb0541499515
* Merge "WiFiInstaller: update usage of ↵TreeHugger Robot2017-03-131-3/+2
|\ | | | | | | WifiManager#addOrUpdatePasspointConfiguration"
| * WiFiInstaller: update usage of WifiManager#addOrUpdatePasspointConfigurationPeter Qiu2017-03-061-3/+2
| | | | | | | | | | | | | | | | | | | | WifiManager#addOrUpdatePasspointConfiguration is updated to return void and throw exception on failure instead of a boolean, so update the callsite accordingly. Bug: 35856174 Test: make -j32 Change-Id: Id56ee82916397a26432a22addfb59ffddddefe79
* | Update DocumentsContract call to ensure thrown Exceptions are handled.Ben Lin2017-03-091-1/+5
|/ | | | | | Test: Build compiles properly. Bug: 36023174 Change-Id: I3dcb3def5877d4a4c5ba4d12ec60ccb4b77426ea
* WiFiInstaller: Passpoint API rename updatePeter Qiu2017-02-021-2/+2
| | | | | | | | | | ConfigBuilder has been renamed to ConfigParser to avoid confusions with the builder pattern used in the Framework API. So update the callsite accordingly. Bug: 34862444 Test: None Change-Id: I71d61a7e6c0a44b7004ca83f927eda008d02cb25
* WifiInstaller: use updated PasspointConfiguration APIsPeter Qiu2017-01-241-4/+4
| | | | | | | | | | | PasspointConfiguration APIs are updated to use private variables with public accessor methods instead of public variables. So update the code to use the accessor methods instead of using variables directly. Bug: 34627062 Test: make -j32 Change-Id: I96e06a16440eba02ea2d39db1ef5a0e5016e0f7a
generated by cgit v1.2.3 (git 2.25.1) at 2026-04-13 19:55:55 +0000