[Android Apps and Games] Daria Adguard Team:
AdGuard 3.6.11!

You must have been missing AdGuard for Android updates. Well, you won't be bored now, because we're breaking into 2023 with a new release of the product, and we'll only gain traction from there.

The main changes in AdGuard v3.6.11 for Android were made in our core filtering engine – CoreLibs and DNSLibs. As for the rest, we’ve worked to enhance content filtering and made a bunch of minor changes to improve the application performance.

Updated DnsLibs to v2.0.75 #4324

A significantly updated version of the DNS filtering library consumes less resources and runs faster. The DNS-over-QUIC protocol implementation now supports the RFC 9250 standard, and the experimental status was removed from the DoQ support.

First step to Encrypted ClientHello support DL#161

First of all, what is Encrypted ClientHello? Nowadays, almost every internet connection is encrypted and no one can see what's inside this encrypted connection. However, there is still one little issue with it: the very first packet of the connection indicates the name of the server you are connecting to. Say you want to open www.google.com, your ISP cannot see what exactly you send and receive from it, but they know what website you are communicating with. ECH (Encrypted ClientHello) is a new technology that is supposed to solve this issue and encrypt that last bit of unencrypted information.

So what would be the first step to supporting it from AdGuard? Surprisingly, it is to suppress ECH! This can be done by switching on both pref.dns.block.ech and pref.https.redirect.doh flags in the Low-level settings.

But fret not: what we want to achieve is to provide you with ECH support globally so that all your apps could benefit from ECH, not just your browser. To accomplish this, AdGuard makes your apps establish regular HTTPS connections with it, and then it will establish a ECH-enabled connection on their behalf. This experimental feature is planned for the next update so stay tuned.

Updated CoreLibs to v1.10.186

DNS-over-HTTPS filtering

Added an option to redirect secure DNS requests to the local DNS proxy #1563

Chrome and Firefox DNS queries sometimes could circumvent DNS filtering by using a DNS-over-HTTPS server. Now AdGuard can automatically filter DNS-over-HTTPS as well.

This feature is experimental and can be enabled in Low-level settings, its name is pref.https.redirect.doh. In the future versions we're planning to enable it by default.

Improved content filtering

The following new features are important to filter maintainers and provide advanced capabilities for content filtering.

Enhancement

Added a new $jsonprune basic rule modifier. This modifier allows advanced filtering for JSON responses #1447

Added a new $hls basic rule modifier. This modifier provides advanced filtering capabilities for modifying HTTP live streaming files which will help with preventing video ads. #1434

Expanded capabilities of the $stealth modifier. Filters maintainers can now specify which Stealth Mode features should be disabled for a given URL. Before that change the only option was to completely disable Stealth Mode. #1224

Added support for empty $path modifier for non-basic rules. #1591

$removeparam can now be applied to POST requests. #1573

Fixed

Hide your Referrer from third-parties Stealth mode option interferes with the $third-party modifier #1640

Cosmetic rules with :where() pseudo-class are rejected #1609

Rules with $third-party modifier block resources from the site's own subdomain #1637

Rules with the $all modifier do not block explicitly visited sites #1590

Other improvements

Enabled HTTPS filtering by default for Soul Browser #4202

Other fixes

When confirming 2FA the code entry page disappears in some cases

AdGuard does not create a local VPN and protection does not start #4269

Internet fails to work when a network is changing from Wi-Fi to mobile data #4265

Compatibility issue with iRobot Home app #4273

This version on GitHub

Download via direct link