Adguard android


AdGuard — Werbeblocker für Android | Übersicht

Hi! We can't wait to tell you about new Adguard for Android version!

It has a little bit for everyone. If you like to have everything under control and customize filtering for every app, check out new settings section - 'Apps & Statistics'. It is much easier now to make your apps behave exactly as you want them to.

For custom filter rules enthusiasts we have a new modifier: $app. Create rules that affect only one specific app, or all other apps except for it.

Those who use Android N devices will save a lot of nerves now - new version of Adguard automatically detects if an app is created specifically for Android N, which allows to avoid many problems (this affects some other potentially problematic apps too).

And everybody will notice a general increase in quality. Many bugs were fixed, many useful changes were made. All details are in the changelog below.

UI

[Added] ‘Apps & Statistics’ settings section #633

We decided to seriously redesign our Firewall section. There will be no more ‘Apps & Settings’ sub-section inside ‘Firewall’. Instead, we introduce a whole new first-level section named ‘Apps & Statistics’. It very much resembles the now gone ‘Apps & Settings’ but has some differences. For example, we got rid of ‘global’ switches - these buttons were too misleading.

Also, you can now disable network access when the screen is off, and you can configure it for each app separately. Not only new connections are not allowed when this option is enabled, but also all existing connections are terminated when the screen goes off.

Another big change is disposal of exclusions lists. Now you can simply add an app to exceptions through the ‘Apps and Statistics’ screen. There are other changes too, and we will not list them all here. We believe the new layout is more intuitive and you will have no troubles navigating through it.

Important note: this is not yet a big redesign we plan to do in Adguard 3.0. Only the tip of the iceberg :)

  • [Added] An option to browse for a file to import user filter #120
  • [Added] A notification to inform user of expiring license #606
  • [Added] New localizations: Slovak & Norwegian Bokmål #688, #717
  • [Changed] Disabled vibration and sound for Adguard notifications #205
  • [Changed] Instead of stopping protection on settings change, a toast message is showed #667
  • [Changed] When user changes default firewall settings, ask him if he wants to reset per-app settings #675
  • [Changed] Show notification when VPN is revoked #672
  • [Changed] Adguard now counts DNS traffic towards a special “virtual” package named “DNS” #668
  • [Changed] Made some minor UI enhancements #684, #685, #687, #692, #697, #698, #700, #721, #726
  • [Fixed] Adguard closes if you swipe it with ‘No icon’ notification setting #662
  • [Fixed] An issue with Samsung’s buggy firmware (messed notification sounds) #716
  • [Improved] Premium features description #669
  • [Improved] UI accessibility for a visually impaired users #519

Ad Blocking

[Added] $app modifier #544

This modifier will be useful for advanced users who create their own custom rules. It allows both blocking ads in a specific app and blocking ads everywhere except for that app. For example, Facebook uses same domains for both ads and useful stuff. This modifier allows to block facebook ads in other apps without breaking the Facebook app itself.

[Fixed] Detect if app targets Android N #653

Due to Android N security policy, HTTPs filtering is impossible for apps developed specifically for Android N, or other apps where user-installed certificates are not trusted. Previously that could lead to errors and app crashes. Now Adguard detects if app targets Android N and does not filter HTTPS for such apps.

  • [Added] RoList filter to the list of supported filters #523
  • [Changed] Several browsers were added to the list of filtered by default #708, #731
  • [Fixed] Disabling filtering for “Android OS” now fully excludes OS packages from the VPN #732
  • [Improved] Added support for the :style pseudo class syntax #701
  • [Improved] Modified $empty modificator behavior to improve filtering #677
  • [Improved] Increased content filtering rules maximum length limit #590

Networking

  • [Changed] Allowed DNS requests for root user #535
  • [Fixed] An issue when allowed apps couldn’t connect when DNS was blocked #714, #720
  • [Fixed] SSL whitelist no more can be applied to random domains #738
  • [Fixed] Resolved shadowing of our Apache commons classes by old versions shipped in Android #709
  • [Improved] All our requests are now more secure with SSL/TLS #611

Install/Update

  • [Added] Automatic protection restart after Adguard update #725
  • [Fixed] Self killing on update #696

Compatibility

From now on it will be much easier for users to add any app to exclusions. No need to go to low-level settings anymore, just open the apps screen in ‘Apps and Statistics’ and add it to exclusions from there.

Following compatibility issues were fixed:

  • Ad blocking interferes with videos in Mail.ru news app #711
  • Upload doesn’t work for Yandex Disk #736
  • Samsung Battery Saving mode #378, #656
  • HTC battery optimization #536
  • Sync for Reddit app #645
  • Cortana voice app #661
  • Lazada app #680
  • Smart appointments in Google Calendar #658

Following apps were added to exclusions due to problems caused by filtering:

Idealo, Mountainview, Itau, Yik Yak, Box, Jet, MeetMe, MoovIt, Waze, Prisma, Grindr, Romeo Uncut, SwiftKey, S Voice, Goes, NU.nl, com.samsung.syncservice, Coursera, Astana Bank, Google Now, Yandex Navigator, Heetch, TomTom Go Mobile, Amazon apps, some banking apps

(Issues: #673, #729, #641, #516, #642, #676, #612, #528, #492, #733, #715, #710, #702, #712, #686, #679, #674, #659, #655, #650, #637, #584, #447, #624, #647)

adguard.com

AdGuard — Adblock for Android | Overview

Hi! We can't wait to tell you about new Adguard for Android version!

It has a little bit for everyone. If you like to have everything under control and customize filtering for every app, check out new settings section - 'Apps & Statistics'. It is much easier now to make your apps behave exactly as you want them to.

For custom filter rules enthusiasts we have a new modifier: $app. Create rules that affect only one specific app, or all other apps except for it.

Those who use Android N devices will save a lot of nerves now - new version of Adguard automatically detects if an app is created specifically for Android N, which allows to avoid many problems (this affects some other potentially problematic apps too).

And everybody will notice a general increase in quality. Many bugs were fixed, many useful changes were made. All details are in the changelog below.

UI

[Added] ‘Apps & Statistics’ settings section #633

We decided to seriously redesign our Firewall section. There will be no more ‘Apps & Settings’ sub-section inside ‘Firewall’. Instead, we introduce a whole new first-level section named ‘Apps & Statistics’. It very much resembles the now gone ‘Apps & Settings’ but has some differences. For example, we got rid of ‘global’ switches - these buttons were too misleading.

Also, you can now disable network access when the screen is off, and you can configure it for each app separately. Not only new connections are not allowed when this option is enabled, but also all existing connections are terminated when the screen goes off.

Another big change is disposal of exclusions lists. Now you can simply add an app to exceptions through the ‘Apps and Statistics’ screen. There are other changes too, and we will not list them all here. We believe the new layout is more intuitive and you will have no troubles navigating through it.

Important note: this is not yet a big redesign we plan to do in Adguard 3.0. Only the tip of the iceberg :)

  • [Added] An option to browse for a file to import user filter #120
  • [Added] A notification to inform user of expiring license #606
  • [Added] New localizations: Slovak & Norwegian Bokmål #688, #717
  • [Changed] Disabled vibration and sound for Adguard notifications #205
  • [Changed] Instead of stopping protection on settings change, a toast message is showed #667
  • [Changed] When user changes default firewall settings, ask him if he wants to reset per-app settings #675
  • [Changed] Show notification when VPN is revoked #672
  • [Changed] Adguard now counts DNS traffic towards a special “virtual” package named “DNS” #668
  • [Changed] Made some minor UI enhancements #684, #685, #687, #692, #697, #698, #700, #721, #726
  • [Fixed] Adguard closes if you swipe it with ‘No icon’ notification setting #662
  • [Fixed] An issue with Samsung’s buggy firmware (messed notification sounds) #716
  • [Improved] Premium features description #669
  • [Improved] UI accessibility for a visually impaired users #519

Ad Blocking

[Added] $app modifier #544

This modifier will be useful for advanced users who create their own custom rules. It allows both blocking ads in a specific app and blocking ads everywhere except for that app. For example, Facebook uses same domains for both ads and useful stuff. This modifier allows to block facebook ads in other apps without breaking the Facebook app itself.

[Fixed] Detect if app targets Android N #653

Due to Android N security policy, HTTPs filtering is impossible for apps developed specifically for Android N, or other apps where user-installed certificates are not trusted. Previously that could lead to errors and app crashes. Now Adguard detects if app targets Android N and does not filter HTTPS for such apps.

  • [Added] RoList filter to the list of supported filters #523
  • [Changed] Several browsers were added to the list of filtered by default #708, #731
  • [Fixed] Disabling filtering for “Android OS” now fully excludes OS packages from the VPN #732
  • [Improved] Added support for the :style pseudo class syntax #701
  • [Improved] Modified $empty modificator behavior to improve filtering #677
  • [Improved] Increased content filtering rules maximum length limit #590

Networking

  • [Changed] Allowed DNS requests for root user #535
  • [Fixed] An issue when allowed apps couldn’t connect when DNS was blocked #714, #720
  • [Fixed] SSL whitelist no more can be applied to random domains #738
  • [Fixed] Resolved shadowing of our Apache commons classes by old versions shipped in Android #709
  • [Improved] All our requests are now more secure with SSL/TLS #611

Install/Update

  • [Added] Automatic protection restart after Adguard update #725
  • [Fixed] Self killing on update #696

Compatibility

From now on it will be much easier for users to add any app to exclusions. No need to go to low-level settings anymore, just open the apps screen in ‘Apps and Statistics’ and add it to exclusions from there.

Following compatibility issues were fixed:

  • Ad blocking interferes with videos in Mail.ru news app #711
  • Upload doesn’t work for Yandex Disk #736
  • Samsung Battery Saving mode #378, #656
  • HTC battery optimization #536
  • Sync for Reddit app #645
  • Cortana voice app #661
  • Lazada app #680
  • Smart appointments in Google Calendar #658

Following apps were added to exclusions due to problems caused by filtering:

Idealo, Mountainview, Itau, Yik Yak, Box, Jet, MeetMe, MoovIt, Waze, Prisma, Grindr, Romeo Uncut, SwiftKey, S Voice, Goes, NU.nl, com.samsung.syncservice, Coursera, Astana Bank, Google Now, Yandex Navigator, Heetch, TomTom Go Mobile, Amazon apps, some banking apps

(Issues: #673, #729, #641, #516, #642, #676, #612, #528, #492, #733, #715, #710, #702, #712, #686, #679, #674, #659, #655, #650, #637, #584, #447, #624, #647)

adguard.com

Вопросы потребления трафика и ресурса батареи

Иногда вы можете заметить, что, согласно встроенной статистике Android, AdGuard расходует большое количество трафика и/или ресурса батареи.

Обе эти проблемы являются двумя сторонами одной медали. Так как в процессе фильтрации весь мобильный трафик проходит через AdGuard, Android считает, что именно AdGuard потребляет его весь. В реальности это, конечно, не так.

Расход батареи и трафика, показываемый в статистике устройства, не соответствует действительности. Дело в том, что Android приписывает AdGuard весь мобильный и Wi-Fi трафик, который был на самом деле потреблен другими приложениями. Из-за этого доля AdGuard значительно повышается, а доля остальных приложений, наоборот, снижается.

Собственная статистика расхода батареи

Чтобы устранить это недоразумение, мы добавили новый раздел «Расход батареи». Вы можете попасть туда, тапнув по иконке батареи на главном экране приложения.

Внутри вы найдёте график, показывающий реальное потребление ресурса батареи AdGuard на протяжении последних 24 часов, с возможностью получить более детальную информацию о почасовом расходе путем нажатия на точки на графике. Кроме того, там же присутствует цифровое изложение релевантной информации и короткое описание технической стороны вопроса.

Реальный пример

На скриншотах ниже показана статистика потребления батареи за ночь и утро.

Из этих скриншотов видно, что:

  1. AdGuard предсказуемо находится наверху сводной таблицы. Это вообще характерно для телефонов (и совсем не характерно для планшетов без 4G, потому что Wi-Fi с точки зрения расхода батареи потребляет намного меньше).

  2. Обратите внимание на количество отправленных пакетов Mobile и Wi-Fi, которые засчитались AdGuard'у ("Mobile packets sent" и "Wi-Fi packets sent") на скриншоте №2.

  3. На скриншоте №3 статистика одного из реальных потребителей трафика, Яндекс.Браузер. На его счет вообще трафика почти не засчиталось, хотя на деле 70% трафика израсходовано именно им.
Сколько заряда батареи на самом деле потребляет AdGuard?

Для начала приведём немного теории и ссылок с необходимыми данными.

  1. Android считает потребление трафика исходя из так называемого Power Profile, который предоставляется каждым производителем: https://source.android.com/devices/tech/power/values.html

  2. Главная часть Power Profile - это набор значений, выраженных в миллиамперах, которые определяют потребление батареи каждым компонентом устройства: https://source.android.com/devices/tech/power/values.html

Например, из таблички по ссылке выше:

wifi.active= 31mA дополнительное потребление в миллиамперах, вызванное передачей данных по Wi-Fi.

radio.active= 100-300mA дополнительное потребление в миллиамперах, вызванное передачей данных по мобильной сети.

cpu.active= 100-200mA дополнительное потребление в миллиамперах, вызванное работой CPU

  1. AdGuard самостоятельно почти не потребляет трафика, так что для оценки потребления батареи отбросим значения "Mobile/Wi-Fi packets" и остановимся на подсчете CPU.

Формула для вычисления потребления:

"CPU TIME (ms)" X "cpu.active" / (60 60 1000) = "POWER USE mAh"

Подставим в эту формулу реальные значения.

Возьмем CPU total из второго скриншота и переведём в миллисекунды: 506000.

Коэффициент cpu.active для 2GHz будет равен примерно 225mA.

Финальный результат:

506000 225 / (60 60 * 1000) = 31,625mAh

Итог

Реальное потребление в разы ниже показанного в статистике Android. Вместо 220mAh оно должно быть в районе 31-40mAh. С другой стороны, потребление браузера должно быть не 66mAh, а около 200mAh.

kb.adguard.com

Adguard для Android 2.9.135

Новая версия приложения для Android сегодня вышла в релиз. Она не слишком богата на новые функции и прочие изменения - в версии 2.10 их будет больше, не говоря уже об Adguard 3.0. Однако, и здесь тоже есть на чём заострить внимание - мы очень серьезно переработали и улучшили Пользовательский фильтр. Читайте ниже, чтобы узнать подробности.

Итак, начнём с главного:

[Улучшено] Переработан Пользовательский фильтр #1279

Любой опыт взаимодействия с Пользовательским фильтром в прошлом нельзя описать никаким иным словом, кроме как "удручающий". Он был неудобным, неуклюжим и медленным. В этой версии многое поменялось.

Во-первых, новый дизайн. Он стал гораздо более "чистым".

Мы объединили все элементы управления в единое меню панели инструментов - добавить правило, удалить все правила, редактировать фильтр, импорт и экспорт.

Во-вторых, теперь у вас есть возможность открыть так называемый "режим редактирования", который превращает фильтр в текстовое поле, доступное для редактирования. Это очень удобно, если нужно скопировать/вставить/удалить несколько строк разом, или же отредактировать несколько правил подряд без необходимости нажимать на каждое из них в отдельности.

Наконец, изменился общий вид фильтра. Правила теперь дифференцированы по цвету, в зависимости от их типа. Отчетливо видны строки-комментарии. Каждое правило может быть отключено и включено обратно, без необходимости удалять и пересоздавать его.

Если вы заинтересованы в создании и поддержании собственного списка правил, вы, без сомнения, найдёте все эти изменения полезными. Лично мы от них в полном восторге! :)

Блокировка рекламы
  • [Добавлено] Фильтр Juvander's Adblock List #1225
  • [Изменено] Диапазон действия правил $$ увеличен #1185
  • [Изменено] Оптимизирована работа с фильтрами (потребление оперативной памяти) #1181
  • [Изменено] Способ обработки правил с модификатором $empty #1274
  • [Исправлено] Модификатор $network не работает #1268
  • [Исправлено] Конструктор правил игнорирует referer #1221
  • [Исправлено] Firefox nightly 64-bit не распознаётся как браузер #1257
  • [Исправлено] Проблема нагрузки на CPU, связанная с постоянными запросами к серверу счетчика #1179
Работа с сетью
  • [Изменено] Обновлен список HTTPS исключений
  • [Изменено] HTTPS больше не фильтруется для приложений без network_security_config, разработанных под Nougat #1286
  • [Исправлено] Проблемы совместимости на Android O #1227
  • [Исправлено] Проблема VPN + IPv6 на Android 4.4.2 #1267
  • [Исправлено] IPv4-адреса обходятся VPN #1026
  • [Исправлено] App preview не работает #973
  • [Исправлено] Проблема промежуточного сертификата SHA-1 #1178
  • [Исправлено] Проблема автоматической паузы на устройствах Nougat #1202
  • [Исправлено] Скорость передачи данных была значительно увеличена #1192
  • [Исправлено] Adguard не фильтрует HTTPS соединения с серверами TLS 1.0 #1195
  • [Исправлено] Переконфигурация iptables при добавлении/замене пакета ведёт к отсутствию интернета #1245
  • [Улучшено] Добавлено восстановление сессии с использованием ID сессии #1238
Пользовательский интерфейс
  • [Добавлено] Добавлены локализации: Португальский (PT) и Персидский #1139, #1189
  • [Изменено] Описание статуса лицензии #1191
  • [Исправлено] Вылет при смене типа сети #1272
  • [Исправлено] Опечатки и ошибки пунктуации #1159, #1186
  • [Исправлено] Макет экрана Журнала Фильтрации #1180
  • [Исправлено] Импорт Пользовательского фильтра не работает на Nexus 9 #1300
  • [Улучшено] Обновлены локализации #1290
Прочее
  • [Изменено] Браузер Yuzu был добавлен в список фильтруемых по умолчанию #1285
  • [Исправлено] Многочисленные проблемы совместимости
  • [Улучшено] Логгирование в случае возникновения критической ошибки #1216

В заключение

Напоминаем, что полный список изменений и вообще всё, что касается Adguard для Android, вы можете найти на GitHub. Вы можете даже задать вопрос разработчикам и получить своевременный ответ! Впрочем, сделать это можно и в комментариях прямо здесь - ждём ваших отзывов!

blog.adguard.com

FAQ | Adguard Knowledgebase

What is Adguard?

Adguard is a remarkable internet filter that protects you from annoying advertising, malicious and phishing websites, online tracking and much more. Adguard handles all types of Internet ads, speeds up page loading, saves bandwidth and increases your device protection against possible threats.

Adguard uses a unique technology that allows filtering the traffic on your device without ROOT privileges. Filtering speed does not depend on the work of VPN server, as it is embedded right in your device.

How does Adguard protection work?

Adguard filters your browser traffic by blocking requests to phishing and malicious websites and removing intrusive browser advertising. Adguard can use two modes of traffic filtering.

  1. Local VPN mode.

  2. Local HTTP proxy mode.

Local VPN mode

If you are using this mode, Adguard does not need ROOT privileges to carry out filtering. At the same time, a VPN-server is located on your device, so that there is no need to pass your traffic through a remote server in order to filter it.

Local HTTP proxy mode

In this mode Adguard launches a local HTTP proxy server on your device. This mode is recommended, if you use a rooted device. Otherwise, manual adjustment of an HTTP proxy will be needed to use this mode, the filtering in mobile networks (Edge/3G/4G) will also be impossible.

Do I need the ROOT access?

Unlike most applications that are engaged in traffic filtering, Adguard does not require ROOT access to your device. In local VPN server mode Adguard, will filter all your traffic and ROOT access is not needed.

How to manually configure a local HTTP proxy?

If your device does not support automatic proxy configuration, then you can configure a proxy server manually, using the instructions below:

In the Adguard Settings select Local HTTP Proxy mode and Proxy setup mode — Manual.

Go to your phone settings and choose Wi-Fi. A list of wireless networks will be opened.

If the device is not yet connected, connect to the Wi-Fi network that you need. Open the network setting by pressing the line with this network. The following menu of the selected Wi-Fi network will appear.

Select Modify network. In the new window select Show advanced options.

In Proxy select Manual.

Enter 127.0.0.1 in Proxy hostname and enter the port that is showed in proxy settings in Adguard application itself (port 8080 is used in Adguard setting by default).

A proxy server has been set up. Now all Wi-Fi traffic will be filtered by Adguard.

How to use a third-party VPN along with Adguard?

If you are already using a VPN for other purposes, then in order for Adguard filtering to work, you can change it to the HTTP proxy server mode. The filtering mode can be changed in the Advanced Settings.

In this mode, there are two ways to set up a proxy: automatic and manual.

Automatic mode

In the automatic mode, enabling of filtering does not require any action from you. Filtering will work in both mobile and Wi-Fi networks. The problem is that the automatic mode can be operated only on rooted devices.

Manual mode

This approach may not work in some situations. It depends on your firmware and the actual VPN app. In some cases traffic bypasses a manually configured proxy.

In the manual mode, filtering will only work in Wi-Fi networks. You will have to manually configure the use of a proxy server for each Wi-Fi network.

What restrictions does a VPN mode have?

Adguard filters traffic using a local VPN-server by default. In this mode there are some restrictions.

When asked to enable VPN, I cannot tick the "I trust" checkbox. Why?

If you are using an application that enhances your display (for example, Night Mode or Twilight), you need to temporarily disable that application. Android prevents your selection for security reasons.

Why do I get a "VPN is not supported" dialog message?

This dialog appears when Adguard fails to create a VPN connection on the device. So far, we've identified the following situations where this can happen.

1. Custom firmware

You're using custom firmware that is missing a tun.ko kernel module needed for proper VPN support on Android.

2. Wrong firmware configuration

The firmware on the device has not been configured correctly. If the manufacturer is aware of the problem, the issue may fixed in future firmware updates.

Restore VPN support

If you have ROOT access you can restore the VPN module (tun.ko) using a special app tun.ko installer.

Switch the filtering mode

You can switch to the Local HTTP Proxy filtering mode in Adguard's extended settings.

Why do Android stats show that Adguard consumed more traffic than it saved?

On Android's Data usage page or in your favorite data-traffic tracking app, you might see an indication that Adguard has consumed all or most of your mobile traffic. Make no mistake - it's your apps and not Adguard that consumed the data in question. There is a known issue with Android when VPN or a proxy is established, with all traffic from all apps being assigned to Adguard.

We hope that this clarifies what's happening.

Why Wi-Fi and USB tethering do not work with Adguard?

Android does not allow tethered connections to route through the VPN. This is an Android rule that applies to all VPN apps running on non-rooted devices. This is done for security, out of concern that if a malicious individual was able to get access to your tether, they could piggyback onto the VPN connection.

Solutions

  1. Disable Adguard when you want to use tethering.

  2. If you have ROOT access, you may switch to the proxy filtering mode instead of using VPN. It may be done in Adguard's extended settings.

Which browsers are not supported by Adguard?

In general, Adguard does not support browsers with traffic compression option. The only browser supported is Google Chrome. We can filter its traffic even if traffic compression is on.

Opera

Adguard can filter the Opera browser, if you don't use the Off-Road mode. Otherwise the traffic is compressed, so we cannot filter it.

Opera Mini

The Opera Mini browser always compresses the traffic so Adguard cannot filter it.

UC Browser

Adguard can filter the UC Browser, if Speed Mode or Cloud Acceleration is disabled. Otherwise some of the traffic is compressed and encrypted so we cannot filter it.

Puffin Browser

The Puffin browser always compresses the traffic so Adguard cannot filter it.

Why a VPN can not be started on Android 5.0?

There are two known bugs of Android 5.0 which may break a VPN start-up. The only solution is to reboot your device.

How to resolve known compatibility issues with other apps?

This section names third-party apps which are known to be incompatible to some degree with Adguard. In some cases, either Adguard or the conflicting app can be configured in some way to resolve the incompatibility.

Orbot: Proxy with Tor

Problem: Orbot: Proxy with Tor is a VPN app and you cannot have two active VPNs at the same time.

Solution: setup Adguard to use Orbot as an outbound proxy.

  1. Run Orbot.

  2. Open Adguard, go to Settings - Advanced

  3. Open Proxy settings

  4. Use the following settings:

Proxy type SOCKS4, host: 127.0.0.1, port: 9050.

  1. Run Adguard protection.

VPN by Private Internet Access

Problem: VPN by Private Internet Access is a VPN app and you cannot have two active VPNs at the same time.

Solution:

  1. Ensure that Adguard protection is started before DroidWall.

  2. Allow Adguard in DroidWall settings.

Opera Max

Problem: Opera Max is a VPN app and you cannot have two active VPNs at the same time.

Solution: (ROOT is required) switch filtering mode to Local HTTP proxy in advanced settings.

Why is the firewall's function partial and the data stats not that accurate in proxy mode?

There are many types of data-traffic on the Internet: the Web, VoIP, Games, VPNs, UDP traffic (including DNS-requests) and so on. In the VPN mode, we control every packet of data that is coming from any app, but in the proxy mode we control only a subset of the traffic. Therefore, we can not guarantee full connection disabling for particular apps and the numbers that you see in Adguards statistics in proxy mode may be inaccurate.

Then, the proxy mode is bad?

Not at all. If you don't care so much about the statistics and the UDP traffic you can use it without hesitation.

Why are some apps excluded?

There are some cases in which some applications need very unconventional ways to communicate through the Internet, or the filtering procedure is breaking some app functionality. Therefore, some applications have to be excluded from filtering. We hope such measures are temporary as we are constantly improving our filtering and network algorithms.

How does DNS filtering work?

Adguard can filter domain resolution requests to the Domain Name System servers, handle them locally, and block requests to phishing, malicious, advertising and tracking systems on such domains.

Blocking is implemented by sending back a specially crafted response that redirects all traffic to local network interface (with 127.0.0.1 IP address).Then the browser or app that intended to connect to such a domain will try to connect to a server on this particular device, and eventually get an error.

Q: If this seems like a best way to filter ads, why use something else?

A: Because there are many advertising systems that use the same domains for advertising and also some useful services. The DNS filtering can be used just to speed up overall filtering process and to save some battery juice.

Q: Why can't I use DNS-filtering with a Local HTTP proxy mode?

A: Because we need to filter all traffic (all network packets) sent from your device for DNS-filtering. Only VPN mode can accomplish such a thing.

How does HTTPS filtering work?

What is HTTPS?

HTTPS is similar to HTTP (Hyper Text Transfer Protocol), but using an encryption protocol (called SSL/TLS), as indicated by the last letter S (Secure). This protocol is used for the transmission of sensitive information, such as MasterCard/Visa card numbers and personal data.

Why should it be filtered?

Now more and more websites, blogs, and social networks are switching to HTTPS. Then, following blogs and websites, more and more ad networks are switching to HTTPS as well, because it is necessary to display ads on the sites working over HTTPS.

The following are examples of popular websites, where ads cannot be removed without HTTPS filtering: youtube.com, facebook.com and twitter.com.

How does the filtering of encrypted traffic work?

If this was easy, HTTPS wouldn't be secure. In order to filter secure traffic, Adguard will create two secure connections. One to a browser, or other application; and another to a server. It is important that in this case the browser "trusts" Adguard and its created connection. For this purpose Adguard generates and installs a special root certificate in the system and, if necessary, in certain browsers e.g. Firefox.

Does my traffic stay secure and encrypted?

Of course! Your connection to the remote server stays encrypted and secure. Just like a browser Adguard checks the server certificate before starting to filter it.

By default, Adguard doesn't filter websites of financial services and websites with important personal data.

There are two modes of HTTPS filtering:

Filter ONLY connections to domains on the blacklist.

Filter ALL connections EXCEPT those to domains on the whitelist. We have pre-added domains of financial institutions and banks there, and this list will be updated in the future.

All right, how can I enable it?

Install certificate into the system certificates storage.

If you do not have a password or lock screen pattern, then Android will require one of the options to be set up. This is an Android requirement.

Restart the protection. If you have done everything correctly, the HTTPS filtering will work like the usual filtering.

How to remove a certificate from the system?

Go to Android settings -> Security -> Trusted credentials.

Go to the "User" section.

Select "Adguard Personal CA" (it might be the only certificate there).

In the opened dialog window scroll down and tap 'Remove'.

kb.adguard.com


Смотрите также