Zum Hauptinhalt springen

Moving the CA certificate to the system store on rooted devices

Infos

Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbeblocker, der Ihr Gerät auf Systemebene schützt. Um zu sehen, wie es funktioniert, laden Sie die AdGuard-App herunter

AdGuard for Android can filter encrypted HTTPS traffic, thus blocking most ads and trackers on websites. On rooted devices, AdGuard also allows you to filter HTTPS traffic in apps. HTTPS filtering requires adding AdGuard's CA certificate to the list of trusted certificates.

On non-rooted devices, CA certificates can be installed to the user store. Only a limited subset of apps (mostly browsers) trust CA certificates installed to the user store, meaning HTTPS filtering will work only for such apps.

On rooted devices, you can install a certificate to the system store. That will allow AdGuard to filer HTTPS traffic in other apps as well.

Here's how to do that.

How to install AdGuard's certificate to the system store​

  1. Open AdGuard → Settings → Filtering → Network → HTTPS filtering → Security certificates.

  2. If you don't have any certificate yet, install the AdGuard Personal CA into the user store. This will allow AdGuard to filter HTTPS traffic in browsers.

  3. Install the AdGuard Intermediate CA into the user store. You'll need it to run the adguardcert Magisk module that allows you to move certificates to the system store.

    Install the certificate *mobile_border

  4. Install the latest release of the adguardcert Magisk module.

  5. Open Magisk → Modules → Install from storage and select the downloaded adguardcert file. The AdGuard Personal CA certificate will be copied to the system store.

    Magisk-Module öffnen *mobile

    Installation aus dem Speicher *mobile

    Select adguardcert *mobile

  6. Tap Reboot.

    Reboot the device *mobile

After the transfer, the AdGuard Personal CA in the system store will allow you to filter HTTPS traffic in apps, while the AdGuard Intermediate CA in the user store will allow you to filter HTTPS traffic in Chromium-based browsers (see below why).

Known issues with Chrome and Chromium-based browsers​

Chrome and other Chromium-based browsers require Certificate Transparency (CT) logs for certificates located in the system store. CT logs don't contain information about certificates issued by HTTPS-filtering apps. Therefore, AdGuard requires an additional certificate in the user store to filter HTTPS traffic in these browsers.

Bromite browser​

In addition to the above issue, Bromite doesn't trust certificates in the user store by default. To filter HTTPS traffic there, open Bromite, go to chrome://flags, and set Allow user certificates to Enabled. This applies to both rooted and non-rooted devices.