Bring back Android 10 KeyChain.createInstallIntent()'s old behavior
Find a file
2024-11-17 15:29:23 -03:00
.github/workflows Add build workflow 2024-11-17 15:20:36 -03:00
app Bump version 2024-11-17 15:29:23 -03:00
gradle/wrapper Update Gradle wrapper 2024-11-17 19:25:39 +01:00
images Add some assets and update README 2023-11-02 20:26:26 -03:00
.editorconfig Initial commit 2023-11-02 20:07:30 -03:00
.gitattributes Initial commit 2023-11-02 20:07:30 -03:00
.gitignore Initial commit 2023-11-02 20:07:30 -03:00
build.gradle Update Android gradle plugin 2024-11-17 15:12:23 -03:00
gradle.properties Initial commit 2023-11-02 20:07:30 -03:00
gradlew Update Gradle wrapper 2024-11-17 19:25:39 +01:00
gradlew.bat Update Gradle wrapper 2024-11-17 19:25:39 +01:00
LICENSE Initial commit 2023-11-02 20:07:30 -03:00
README.md Update README 2024-11-17 15:17:22 -03:00
settings.gradle Initial commit 2023-11-02 20:07:30 -03:00

Nel

Bring back KeyChain.createInstallIntent's old behavior to Android 11+.

Why

Android 11 introduced a restriction where the KeyChain.createInstallIntent method can no longer be used to install CA (Certificate Authority) certificates. As of today, most apps that relied on this old behavior have already been updated to work around this; however, there are still some apps that rely on the old behavior (e.g., HTTP Canary).

1

This module will (hopefully) make them work correctly on Android 11+.

1

Usage

Just install and reboot the device. If you are using LSposed, you just need to mark the "Certificate Installer" package on the list of apps and then kill/force-close the com.android.certinstaller process (e.g., by running /system/bin/am force-stop com.android.certinstaller on a terminal emulator).

Supported Android versions

This module was only tested on Android 13-15, but should work on any device running Android 11 or higher.