Skip to content

Commit

Permalink
Merge pull request #345 from AdguardTeam/update-translations
Browse files Browse the repository at this point in the history
Update translations
  • Loading branch information
el-termikael authored Nov 20, 2023
2 parents c6f76b6 + bc874ee commit 5267fa3
Show file tree
Hide file tree
Showing 452 changed files with 9,239 additions and 7,619 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ There are three pre-configured protection levels. Here’s what features they ha

a. *Block trackers*. This setting protects against online counters and web analytics tools using AdGuard’s Tracking Protection filter

b. *Ask websites not to track you*. This setting sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) requests to the websites you visit, asking web apps to disable tracking of your activity
b. *Ask websites not to track you*. This setting sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity

c. *Remove X-Client-Data header*. This setting prevents Google Chrome from sending its version and modification info to Google domains (including Double Click and Google Analytics)

Expand Down Expand Up @@ -452,3 +452,79 @@ Due to additional security measures of Android apps, some AdGuard features are o
- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices
- The [**Automatic proxy** routing mode](#routing-mode) requires root access due to Android's limitations on system-wide traffic filtering
- The **Manual proxy** routing mode requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard

## Assistant

Assistant is a handy tool to quickly change app or website settings and view statistics without launching the AdGuard app.

### How to access Assistant

1. On your Android device, swipe down from the top of the screen to open the notification shade.
2. Find and **expand** the AdGuard notification.

![Expand AdGuard notification in the notification shade *mobile](https://cdn.adtidy.org/blog/new/jkksbhassistant-shade.png)

3. Tap *Assistant*.

![Tap Assistant *mobile](https://cdn.adtidy.org/blog/new/1qvlhassistant-tap-assistant.jpg)

### How to use Assistant

When you open Assistant, you will see two tabs: **Apps** and **Websites**. Each of them contains a list of the recently used apps and websites respectively.

![Assistant main *mobile](https://cdn.adtidy.org/blog/new/i5mljAssistant-main.jpg)

### Apps tab

After you select an app (**let's take Chrome as an example**), you'll get a few options of what you can do.

![Assistant Chrome menu *mobile_border](https://cdn.adtidy.org/blog/new/e1sr4Chrome-assistant.jpg)

#### Recent activity

You'll be taken to the AdGuard app, where you'll see detailed info on the last 10K requests made by Chrome.

![App recent activity *mobile_border](https://cdn.adtidy.org/blog/new/66hpechrome-recent-activity.png)

#### App statistics

You'll be taken to the AdGuard app, where you'll see detailed statistics about Chrome:

- Number of ads and trackers blocked in Chrome
- Data saved by blocking Chrome's ad or tracking requests
- Companies that Chrome sends requests to

#### App management

You'll be taken to the AdGuard app screen where you can disable AdGuard protection for the app.

#### Firewall settings

You'll be taken to the AdGuard screen where you can change Firewall settings for the app, meaning you can manage the app's Internet access.

### Websites tab

![Assistant websites tab *mobile](https://cdn.adtidy.org/blog/new/74y9rAssistant-websites.jpg)

Select a website (**let's take google.com as an example**) and you'll see few options of what you can do.

![Assistant google.com info *mobile](https://cdn.adtidy.org/blog/new/tht0tgoogle-com-assistant.jpg)

#### Add to allowlist

Tapping this option will instantly add google.com to allowlist, and AdGuard will no longer filter it (meaning ads and trackers won't be blocked for the website).

#### Recent activity

You'll be taken to the AdGuard app, where you'll see detailed info on the last 10K requests to google.com.

![website recent activity *mobile_border](https://cdn.adtidy.org/blog/new/xq7f3assistant-website-recent-activity.png)

#### Website statistics

You'll be taken to the AdGuard app, where you'll see detailed statistics about google.com:

- Number of blocked ad and tracking requests to google.com
- Data saved by blocking ad and tracking requests to google.com
- Apps that send requests to google.com
- Information about google.com's subdomains
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: Moving CA certificate to System store on rooted devices
title: Moving the CA certificate to the system store on rooted devices
sidebar_position: 14
---

Expand All @@ -9,68 +9,44 @@ This article covers AdGuard for Android, a multifunctional ad blocker that prote

:::

AdGuard for Android provides a feature called [HTTPS filtering](../../overview#https-filtering) that makes it possible to [filter encrypted HTTPS traffic](/general/https-filtering/what-is-https-filtering) on your Android device. This feature requires adding the AdGuard's CA certificate to the list of trusted certificates.
AdGuard for Android can [filter encrypted HTTPS traffic](/general/https-filtering/what-is-https-filtering), 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 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.

However, on rooted devices, you can install the certificate to the **System store** and allow HTTPS filtering of other apps' traffic too.
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 System store (on a rooted device)
## How to install AdGuard's certificate to the system store

1. Enable HTTPS filtering in AdGuard for Android and save AdGuard's certificate to the User store (use [this instruction](../../overview#https-filtering) if needed)
1. Open *AdGuard → Settings → Filtering → Network → HTTPS filtering → Security certificates*.

From AdGuard for Android v4.1 and after users can install two certificates to the User store, which will help to filter websites in Chrome browser.
1. 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.

1. Go to **AdGuard app****Menu** (≡) → **Settings****Network****HTTPS filtering****Security certificate** → tap “**Copy to the system store**
1. **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.

That is enough for older versions of Magisk.
![Install the certificate *mobile_border](https://cdn.adtidy.org/blog/new/asx1xksecurity_certificates.png)

However, if you have a newer version, you will get this message:
1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/).

> Unable to copy the certificate to the system store. Try using “AdGuard Certificate” module.
In that case, proceed to steps below:

1. Go to **Magisk****Settings**

![Open Magisk settings *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-1.png)

1. Enable **Zygisk**

![Enable Zygisk *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-2.png)

![Go back to Magisk main screen *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-3.png)

1. Download the `.zip` file (of “AdGuard Certificate” module) from the [latest release on GitHub](https://github.com/AdguardTeam/adguardcert/releases/latest/)

1. Go to **Magisk****Modules****Install from storage** and select the downloaded `.zip` file
1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store.

![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png)

![Install from storage *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-5.png)

![Select AdGuard certificate module *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-6.png)
![Select adguardcert *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-6.png)

1. Reboot
1. Tap **Reboot**.

![Reboot the device *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-7.png)

If a new version of "AdGuard certificate" module comes out, repeat steps 3-7 to update the module.
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).

The module does its work during the system boot. If your AdGuard certificate changes, you'll have to reboot the device for the new certificate to be copied to the system store.
## Known issues with Chrome and Chromium-based browsers

### Bromite browser

:::note
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.

In order for the **Bromite** browser to work properly, in addition to the steps mentioned above, you need to set "Allow user certificates" in `chrome://flags` to "Enabled" state.

:::

### Chrome and Chromium-based browsers

Long story short, you will have no problems with HTTPS filtering in Chrome and Chromium-based browsers on rooted devices, if you use "AdGuard Certificate" module.
### Bromite browser

Here is a bit more detailed explanation: Chrome (and subsequently many other Chromium-based browsers) has recently started requiring CT logs for CA certs found in the **System store**. "AdGuard Certificate" module copies AdGuard's CA certificate from the **User store** to the **System store**. It also contains a Zygisk module that reverts any modifications done by Magisk for [certain browsers](https://github.com/AdguardTeam/adguardcert/blob/master/zygisk_module/jni/browsers.inc). This way the browsers only find AdGuard’s certificate in the User store and don’t complain about the missing CT log, while other apps continue to use the same certificate from the System store.
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**.
Original file line number Diff line number Diff line change
Expand Up @@ -112,14 +112,11 @@ Or you can configure remove parameters manually:

`setting by name`: server:MyServer

`manually settings`: server:host=1.2.3.4&port=80&type=SOCKS5&username=foo&password=bar&udp=true

`manually settings`: server:host=1.2.3.4&port=80&type=SOCKS5&username=foo&password=bar&udp=true

:::

-----

**Don't forget to include the password as an extra and mention package name and class! You need to do so for every intent!**
**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.**

Extra: `password:*******`

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Find **ALLOW THESE EXTENSIONS** section and then find **AdGuard** among the avai

Tap it, then turn on the switch. On the same screen make sure that the AdGuard extension has required permissions: **All Websites** should have the *Allow* status.

![settings extensions](https://cdn.adtidy.org/public/Adguard/kb/iOS/webext/settings4_en.png)
![settings extensions *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/webext/settings4_en.png)

:::note

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ Another vital part of the Ad Blocker module are its User rules. If you have some

DNS filtering is one of the most useful features, thanks to which all your DNS traffic is encrypted. But if you're using the default DNS server provided by your ISP, your DNS traffic is likely not encrypted and vulnerable to snooping and hijacking.

In the DNS panel you can select the DNS servers from known DNS providers or even add custom DNS servers. Also you can add domains to DNS blocklist or allowlist and add complicated rules using DNS rules syntax. Finally, you can [add DNS filters of your choice](https://filterlists.com).
In the DNS panel you can select the DNS servers from known DNS providers or even add custom DNS servers. Also you can add domains to DNS blocklist or allowlist and add complicated rules using DNS rule syntax. Finally, you can [add DNS filters of your choice](https://filterlists.com).

## Stealth Mode

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ There are three significant reasons why you might want to explore the DNS protec

![DNS Protection *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/dns-settings.png)

In the DNS protection module of AdGuard for Windows you can select the DNS servers from known DNS providers, including [AdGuard DNS](https://adguard-dns.io/kb/) that blocks ads and trackers, AdGuard DNS Family Protection that in addition blocks adult content, or AdGuard DNS Non-filtering that provides a secure and reliable connection, but doesn't filter anything. You can even add custom DNS servers. Also there is an option to add custom rules using [DNS rules syntax](https://adguard-dns.io/kb/general/dns-filtering-syntax/). And if necessary, you can add [DNS filters of your choice](https://filterlists.com).
In the DNS protection module of AdGuard for Windows you can select the DNS servers from known DNS providers, including [AdGuard DNS](https://adguard-dns.io/kb/) that blocks ads and trackers, AdGuard DNS Family Protection that in addition blocks adult content, or AdGuard DNS Non-filtering that provides a secure and reliable connection, but doesn't filter anything. You can even add custom DNS servers. Also there is an option to add custom rules using [DNS rule syntax](https://adguard-dns.io/kb/general/dns-filtering-syntax/). And if necessary, you can add [DNS filters of your choice](https://filterlists.com).

### Parental Control

Expand Down
Loading

0 comments on commit 5267fa3

Please sign in to comment.