Versions history | AdGuard

A small bug has crept into the release. That’s why we’re publishing a hotfix today: so you can enjoy the service, and we can get on with some bigger tasks.

There are two major changes in AdGuard v2.16 for Mac. The first one is the differential filters update. The second is the userstyles support. Let’s take a closer look at each of them and find out how these new features can be useful for you.

Faster filter lists update

Filter lists are what make ad blockers work. Before, even small changes to a list forced the app to re-download the whole rule set, which was slow and inefficient. Now AdGuard for Mac uses differential updates, downloading only the changes that were made since the last update. This reduces server load and speeds up the process. With more frequent updates, you’ll always have the most effective ad blocking.

Customized browsing

Our new feature will help you add more color to your browsing experience. Userstyles make it possible to modify websites’ appearance without altering its content by applying custom CSS. They work like userscripts but focus on styling. Upload or create your own userstyles directly in the app to personalize your browsing experience.

To add a userstyle, go to Settings → Extensions → Add → Import from file or URL. You can find ready-to-use userstyles online or create your own by clicking Add → Create userstyle.

We’ve also updated the filtering engines (DnsLibs and CoreLibs), JavaScript enhancement for filtering rules (scriplets) and fixed a few bugs. Update your app to the latest version now and experience all the improvements for yourself.

Changelog

Improvements

Added support for userstyles #1451

Implemented differential updates for filter lists #1330

Added support for the Floorp browser (Firefox fork) #1446

Fixes

Incorrect Network Extension permission path on macOS Sequoia #1434

Unable to complete installation of AdGuard v2.15 on macOS Catalina #1503

Ads are not blocked in Safari on macOS Sequoia with iCloud Private Relay enabled #1467

DnsLibs (DNS filtering engine)

DnsLibs updated to v2.5.51 #1502

Block RFC9462 (_dns.resolver.arpa) queries #228

The $dnsrewrite=IPv4 rule does not block IPv6 resolution #224

Use pretty_str() in errors reported in DnsRequestProcessedEvent #223

CoreLibs (Filtering engine)

CoreLibs updated to v1.16.45 #1487

Improvements

Support redirection to destination without using tracking services as intermediaries #1557

Enable post-quantum cryptography when it's used by the filtered app #1916

GM_xmlhttpRequest now supports the Referer header #1899

Fixes

sony.de — login is broken in Firefox #1867

AdGuard "content script" is blocked by CSP on uber.com #1903

The "K" string is removed #1910

Scriptlets (JavaScript enhancement for filtering rules)

Scriptlets updated to v1.11.27 1472

Improvements

set-local-storage-item — added allowed and denied values #445

abort-on-stack-trace — support line number for inlineScript and injectedScript #439

set cookie — added checked and unchecked values #444

trusted-click-element — added reload option #301

Fixes

log-on-stack-trace — player is broken on deltabit.co #384

“Dear developers, can we get a bugfix pronto?” Of course you can! Right after the release, we serve you a hotfix with a resolved problem and fine-tuned operation.

Have you ever shared your settings? This feature comes in handy when you don't want to reconfigure everything on a new device, or when you want to report missed ads. In the new version, sharing settings has become even easier: to export settings, simply go to Settings → Advanced → Share settings…, and to import them, open the resulting link in your browser and click Import.

There have also been updates to the CoreLibs filtering engine, so there will be fewer crashes and more modifiers: $xmlprune and $urltransform. Now even more distracting page elements will be blocked.

Changelog

Improvements

Implemented Configuration import via URL for macOS #1428

Fixes

Open settings button text is missing for Safari Assistant on macOS Big Sur #1366

CoreLibs (filtering engine)

CoreLibs updated to v1.15.64 #1456

Improvements

Added $urltransform (trusted) modifier support #1364

Added $xmlprune modifier support #473

Added mobile browsers to the list of user agents that natively support ':has()'. #1870

Allowed ECDSA ciphers on local side #360

Set up Sec-Fetch-Dest: fencedframe #1853

Added support for the uBO /regex/ format (cosmetic rules) #1844

Fixes

AdGuard filtering stops working after VPN is enabled #1189

Adblock syntax rules with FQDN do not work #210

AdGuard and FTP connection error #1864

Userscript XHR errors #1876

$all modifier does not work with non-domain URL part#1860

URL blocking rules do not work correctly with the $generichide modifier #1857

UserscriptsWrapper

UserscriptsWrapper updated to v1.2.24

Fixes

vk-metabot.user.js does not work with AdGuard #1871

ContentScript

ContentScript updated to v2.0.6

Fixes

Element-hiding rules ## and #$# do not apply to tv.rambler.ru #1865

DnsLibs (DNS filtering engine)

DnsLibs updated to v2.5.34 #1436

This is a technical update aimed to increase the app stability and fix minor bugs.

If you were one of the few users who experienced high CPU usage by AdGuard, we are happy to inform you that we have fixed it in this patch, as well as updated CoreLibs and DnsLibs.

Changelog

Fixes

High CPU usage #1407

CoreLibs (Filtering engine)

Updated CoreLibs to v1.14.57 #1423

DnsLibs (DNS filtering engine)

Updated DnsLibs to v2.5.25 #1421

The AdGuard v2.14 for Mac features the usual bug-fixes-for-better-performance changes, but not only that! This time, the star of the show is the CoreLibs update, which brings improvements to the app overall, with two notable features in particular. First up, we’ve fine-tuned the Encrypted ClientHello support. Yes, it’s still in the experimental phase, but our team has identified several issues that were holding back the seamless activation of ECH by default. With this release, we’ve addressed them and paved the way for enhanced performance. Additionally, the updated CoreLibs now provide the ability to filter DNS-over-HTTPS requests on the fly. This means that AdGuard by default won’t redirect DoH queries to another DNS server, and instead queries will still be sent to the server chosen in the browser. The old behavior may be restored by turning off network.dns.filter.secure.request.transparently.enabled in the advanced settings. This update also includes other minor changes. If you’d like to, feel free to dig into each one of them by reading our extensive changelog below.

Changelog

Fixes

Buttons do not respond on the Proxy Configuration screen in some cases #1327

CoreLibs (Filtering engine) updated to v1.14.51

Improvements

Indicate that outbound proxy is used in the request processed event #1385

Support for passing host to outbound proxy #1386

User rules editor improved #1402

Fixes

Apply $permissions only to document #1856

Cannot parse QUIC ClientHello split into two packets #1861

Cookie rules with [ and ] in the name considered as invalid #1843

Cosmetic rules are not applied in some cases when AdGuard works alongside AdGuard VPN browser extension #1791

VOT (Voice over translation) script does not work in Google chrome #1665

$all modifier does not work correctly #1842

mall.sk content script is not injected #1834

Other

Added Firefox 121.0+ to the list of user agents, which support :has() natively #1840

Added an option to use | as a separator in $permissions #1850

Blocking regex rule that has escaped slash in a character class does not work #1831

Content script is not injected if there is a tag (with embed attribute) before doctype declaration #1825

Get ECH parameters from intercepted DNS HTTPS queries #1794

Improved HTML filtering performance #1855

On-the-fly filtering of DoH connections #198

Support anti-DPI feature for Korea Telecom #1789

$path modifier does not work with query params #1817

$removeparam on url with port redirects to url without port #1818

AdGuard breaks the android-hilfe.de website #1800

Cannot connect to wiki.cemu.info securely #1821

DnsLibs (DNS filtering engine) updated to v2.5.18

Improvements

Allow specifying tcp-only and udp-only DNS upstreams #208

Support passing hostname to outbound proxy instead of bootstrapping #197

Other

Improved handling of HTTPS rrtype #215

Happy Eyeballs used for IPv4/IPv6 in DoH #217

UserscriptsWrapper updated to v1.2.23

Added GM.xmlhttpRequest as alias of GM_xmlhttpRequest #1785

Scriptlets (JavaScript enhancement for filtering rules) updated to v1.10.25

Improvements

Added compatibility with uBO’s set-cookie scriptlet #332

Added new scriptlet — call-nothrow.js #333

Added new scriptlet — spoof-css #317

Added new scriptlet — trusted-create-element #278

set-cookie — added more supported values #379

google-analytics — added ga.q property #355

google-ima3 — added OmidVerificationVendor property #353

Added new scriptlet — href-sanitizer #327

Added new scriptlet — json-prune-fetch-response #361

Added new scriptlet — json-prune-xhr-response #360

Added new scriptlet — trusted-suppress-native-method #383

set-cookie — increase a possible numeric value #388

trusted-click-element — add support for finding selectors in shadowRoot #323

Use some redirects resources as scriptlets as well #300

New scriptlet — trusted-set-attr #281

New scriptlet — no-protected-audience #395

Added possibility to allowlist scriptlets #377

Improved prevent-fetch — add cors responseType #394

Improved set-cookie — add 'domain' parameter #389

Fixes

set-constant — setProxyTrap() #403

set-cookie — do not encode a cookie name #408

set-local-storage-item conversion — '$remove$' param #404

We are excited to announce AdGuard v2.13 for Mac. This version contains several under-the-hood improvements and bug fixes to enhance your browsing experience. But more importantly, we have implemented a useful ad blocking tool. Let’s take a closer look at the main improvements.

More transparency to HTTPS filtering

To enhance the transparency of HTTPS filtering, AdGuard now offers the option to inspect the original certificate via Filtering Log. There you can view details of any web request, examine the encryption used by AdGuard, and inspect the original certificate.

This feature stems from a major concern with HTTPS filtering. AdGuard validates the certificate (and does it well!), but there may be situations where you’d like to inspect the original certificate yourself. You can read more about this issue in our Knowledge base.

Support for selectors in HTML filtering rules

The big change in this version is the improved HTML filtering. We’ve added support for selectors in HTML filtering rules, which helps block ads more effectively.

New DnsLibs and Basic HTTP authentication

With this DnsLibs update, AdGuard for Mac users gain access to a new feature: Basic HTTP authentication. What does it mean?

Imagine you have a custom DNS server and want to restrict access to it. You could restrict access by IP address (for example, only allow your home IP to connect to the DNS server), but what if you have a mobile device that frequently changes networks?

Luckily, DNS-over-HTTPS protocol allows us to benefit from features of HTTP protocol, and one of them is the authentication option. When adding a custom DNS server that supports HTTP authentication in AdGuard for Mac, you can now include authentication information that will be used to connect to that server.

Soon Basic HTTP authentication will be available in AdGuard Home and AdGuard DNS, you will be the first to know!

We have also fixed some minor issues as well as improved AdGuard’s performance and stability. We hope you’ll enjoy the new version of AdGuard v2.13 for Mac.

Changelog

Improvements

Add Vivaldi support for AdGuard Assistant #998

Indicate the HTTPS filtering state and the original certificate in the Filtering log #1284

Fixes

Failed to stop/start the DNS service #1311

WARP gets the "Unable to connect" error if AdGuard is running #1234

Wi-Fi authorization popup doesn't show up while AdGuard is on #892

DNS filtering breaks Tunnelblick VPN #1310

CoreLibs (Filtering engine)

Updated CoreLibs to v1.13.115

Removed an option to move a certificate #277

Added support anti-DPI feature for Korea Telecom #1789

Improvements

Added !#else preprocessor directive support #1806

Adopted new rule priority scheme #1768

Changed sec-ch-ua headers to match User-Agent when Stealth Mode is active #1764

Improved HTML filtering performance #1772

Improved usage of ECH retry_configs #1793

Fixes

Images are not displayed in Edge Bing Chat #1744

Websites using SXG have no cosmetic filtering when opened from Google search #1812

The filtering on the macperformanceguide.com website doesn’t work #1810

UDP timeout is too small in TCP/IP stack #1796

One of the subdomains is not filtered due to different site certificates #1839

DnsLibs (DNS filtering engine)

* Updated DnsLibs to v2.4.36

#### Improvements

Added basic auth for DoH endpoints #189

Allowed sharp comment in exact domain name rules #196

Fixes

Possible DoS attack against the local DNS proxy when it's using a plain DNS upstream #202

DoH is trying to use stale connection for too long #200

Made so that type=HTTPS requests are now filtered properly #199

Important for filter maintainers

Added $extension modifier disabling specific userscript #1706

Improved HTML filtering rules $$ and allowed CSS-like selectors #94

Added support for cap_html_filtering condition #1758

$denyallow does not allow blocking documents #1809

$stealth exceptions do not work on the TCP stack level where we block STUN/TURN #1737

Content script is not injected into elements loaded in object tag #1769

Detect website locale based on HTML "lang" attribute and language request HTTP headers, automatically activates the language-specific filters #1736

Increased response size limit to 10 MB for $replace, $hls and $jsonprune #326

Scriptlets (JavaScript enhancement for filtering rules)

Updated Scriptlets to v1.9.101

Improvements

Improved prevent-fetch #364

Improved storage item scriptlets — add regexp support for items removing #256

Added new trusted scriptlet trusted-prune-inbound-object #372

Added more supported values for set-cookie #375

Improved set-local-storage-item, set-session-storage-item — added support “on” and “off” #366

Handle uBO’s syntax $redirect priorities #59

Improved xml-prune — support xpath for text content matching #325

Added API method to convert redirects based on their name #346

Improved json-prune — stack #348

Improved prevent-xhr — multiple requests #347

Fixes

googletagservices-gpt lacks the setPrivacySettings method #344

set-constant scriptlet breaks vimeo.com #380

Fixed set-constant scriptlet when maximum call stack size is exceeded #373

Fixed set-constant — no value override #330

Fixed trusted-replace-xhr-response — breakage on music.youtube.com #359

Improved m3u-prune — content is not pruned if contains carriage return #354

Improved trusted-replace-fetch-response — do not replace content if URL is set by Object.defineProperty #367

Escaped commas in the params during conversion to uBO rules #343

UserscriptsWrapper

Updated UserscriptsWrapper to v1.2.21

The 网盘直链下载助手 userscript is not working with AdGuard #1780

Attention Mac users, we have an urgent release! AdGuard v2.12.2 for Mac addresses a critical issue affecting Firefox users. With AdGuard enabled, some websites would not load and would display the error about a potential security risk.

Changelog

Fixes

HSTS/SSL errors in Firefox #1326

CoreLibs (Filtering engine)

CoreLibs updated to v1.12.83 #1324

In the previous version of AdGuard for Mac, some users encountered the issue when the “AdGuard wants to make changes” prompt appeared after every system reboot. In AdGuard v2.12.1 for Mac, we’ve fixed this bug and updated CoreLibs and DnsLibs.

Changelog

Fixes

AdGuard constantly asks to enter administrator password after reboot #1307

In 'have-result' state the connection has timed out #1180

AdGuard blocks all the requests to a .local domain when you use 127.0.0.1 local rule #207

CoreLibs

Updated CoreLibs to v1.12.78 #1308

DnsLibs

Updated DnsLibs to v2.2.36 #1314

We are happy to announce the release of AdGuard v2.12 for Mac! This time we have worked a lot to improve your privacy and user experience. Please note that this version of AdGuard for Mac no longer supports macOS High Sierra 10.13 and Mojave 10.14. If you are currently using an older version of Mac, please download the previous version of AdGuard.

AdGuard v2.12 for Mac beta boasts significant improvements. Before AdGuard for Mac could only filter HTTP/1 and HTTP/2 traffic. In v2.12 we have updated CoreLibs so now users can enable HTTP/3 filtering. HTTP/3 (HTTP-over-QUIC) is the latest version of the HTTP protocol that uses QUIC instead of TCP. The QUIC network protocol has a lot of advantages over the TCP transport layer protocol. It provides increased privacy and security, a more stable and faster Internet connection, etc. Enabling HTTP/3 filtering allows you not just to use all the advantages of QUIC protocol, but also block advertisements and trackers! Now our users can enjoy fast Internet connection without any disturbance.

Currently, HTTP/3 filtering is an experimental feature. Also, due to a browser-specific bug, this feature is now broken in Chrome. However, it should work fine in Safari and Firefox. To use HTTP/3 filtering, go to Advanced → Advanced Settings → network.https.filter.http3.enabled.

We have also fixed compatibility issues with WARP, updated Scriptlets, CoreLibs and DnsLibs.

Changelog

Features

Experimental HTTP/3 filtering support #1253

Fixes

AdGuard is not blocking ads in "Web Apps" on macOS Sonoma by default #1292

The pointer does not change when hovering over the update button #1244

The app is installed with one non-recommended annoyances filter instead of 5 recommended ones #1263

Important for filter maintainers

Features

Added $method modifier for basic rules #1713

Allowed $stealth rules with empty pattern #1762

Fixes

$jsonprune, $replace, $hls do not work with non-GET-POST HTTP methods #1743

$path modifier does not work on the path market.yandex.ru/? #1726

$jsonprune modifier should be able to handle quotes for jsonp #1734

$network rules does not work on macOS with kext #1773

Consider :has(), :not(), :is() as a standard pseudo-class if ExtendedCss usage is not forced by #?# rule marker #1683

Scriptlets

Scriptlets updated to v1.9.62

Features

Added API method to convert redirects based on their name #346

Improved trusted-replace-fetch-response/trusted-replace-xhr-response — add ability to replace all matched content #303

Added new scriptlet evaldata-prune #322

Added new scriptlet remove-node-text #318

Added new scriptlet trusted-replace-node-text #319

Fixes

Added new way for returning supported values of set-constant scriptlet #316

cannot apply rule message removed for logging scriptlets #313

AdGuard takes commas into account when converting rules to uBO rules #343

Improved prevent-xhr scriptlet #347

log-addEventListener — a lot of errors are printed to console #335

Scriptlets prevent-fetch, prevent-xhr do not help if a request/domain is blocked by DNS filtering #334

Added Accept and Reject values for set-cookie #336

Made case-insensitive values for set-cookie #342

Modified google-ima3 to avoid conflict with the DAI SDK #331

Modified storage item scriptlets to add ability to remove item by key #338

Mock getResponseHeader() and getAllResponseHeaders() methods for prevent-xhr and trusted-replace-xhr-response #295

Fixed issue with pruning when addEventListener was used before calling send() method in m3u-prune and xml-prune scriptlets #315

Added ability for prevent-element-src-loading scriptlet to prevent inline onerror and match link tag #276

trusted-set-cookie-reload — website is not reloaded if $now$ value is used #291

Cookie setting scriptlets — name and value encoding problem #311

Instance properties of Response issue in scriptlet and redirect #297

Value encoding problem with trusted-set-cookie and trusted-set-cookie-reload scriptlets #320

Fixed googletagservices-gpt — updateTargetingFromMap() #293

Scriptlets should handle escaped quotes correctly #286

The application now reflects the version from which scriptlets or redirects are supported #273

Versions

Updated CoreLibs to v1.12.75 #1294

Updated DnsLibs to v2.2.27 #1299

CoreLibs

Features

Added support for HTTP/3 (IETF QUIC) ("h3" protocol) #487

Migrated to the new XPC interprocess communication system #1675

Added $to modifier #1714

Added $referrerpolicy modifier #135

Fixes

uBO media queries are not supported #1707

WARP gets an error "unable to connect" if AdGuard is already running #1234

A few seconds delay when visiting ipTIME home routers #1756

AdGuard desktop version with ECH setting blocks access to domains if VPN extension is enabled #1751

AdGuard slows down WebPage loading time #1522

Exception rules interfere with each other #1749

Hide referer with "Hide your search queries" option enabled if request made by click #1766

Cosmetic rules don't work at mypikpak.com #1767

When the network.https.ech.enabled setting is enabled, ECH GREASE is enabled for sites that do not support ECH #1781

Error when processing script text decryption key not found #1750

Sometimes DNS fallbacks helper returns 127.0.0.1 instead of provider's servers #1687

TCP/IP: Added new reject mode - ICMP administratively prohibited #1774

UDP timeout is too small in TcpIpStack #1796

User script SaveFrom helper gives an error when downloading video from ok.ru site #1776

DnsLibs

Features

Add "lb._dns-sd._udp.*.in-addr.arpa" to the default list of exclusions #194

Fixes

DoH tries to use stale connection too much time #200

sdns:// cert pinning is incorrect #205

Do not direct 127.0.0.1 into outbound proxy #195

UserscriptsWrapper

UserscriptsWrapper updated to v1.2.20

Fixes

User script for imdb.com doesn’t work #1729

In this version we've made it easier to navigate the Advanced settings: they are sorted in alphabetical order, their names can be copied, and column width can be adjusted. Plus, now there is a link to the dedicated Knowledge base article. Besides, we've fixed a few bugs and updated Dnslibs.

Changelog

Features

Improved Advanced settings #1222

Added Vietnamese localization #1224

Fixes

Browser Assistant icon randomly turns gray in v2.10.1 #1247

Can't select items to block on baidu.com in Safari #1246

Can't export settings while using outbound proxy #1249

Typo in the About section in Czech #1225

Versions

Updated DnsLibs to v2.2.5 #1243

With this patch, we've fixed a bug that caused some userscripts with unicode in the name of the main userscript not to work. We've also made some changes to the experimental support for Encrypted ClientHello (ECH) to ensure that it now works in Kext and Automatic Proxy filtering modes. Finally, as usual, we have updated CoreLibs and DNSLibs.

Changelog

Fixes

The ECH feature does not work with Kext and PAC filtering mode #1226

The path modifier does not work on yandex.ru/images #1738

Custom userscripts do not work after updating to v2.10 #1229

Important for filter maintainers

$permissions now use Structured Field Values syntax instead of CSP syntax #1748

Versions

Updated CoreLibs to v1.11.98 #1237

Updated DnsLibs to v2.1.38 #1236

AdGuard v2.10 for Mac brings many new features and various changes.

DNS filtering enabled by default

DNS protection is now enabled by default for all users. If you are not using any DNS server, the system DNS server with the AdGuard DNS filter will be automatically selected. This change was partially necessary to implement another important feature: experimental support for Encrypted ClientHello (ECH).

Experimental Encrypted ClientHello support

What is Encrypted ClientHello?

Nowadays, almost every HTTPS connection is encrypted and no one can see what’s inside it. However, the very first packet of the connection, called ClientHello, 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. This is where Encrypted ClientHello (ECH) comes in handy. It encrypts this last bit of unencrypted information, making your HTTPS connection fully encrypted. This means that third parties, such as your ISP, will not be able to see what is inside the connection or which site the connection was made to.

AdGuard is not the only one working to support ECH. Browsers such as Chrome and Firefox are also in the process of adding ECH support. However, AdGuard has a significant advantage.

Assuming that Chrome has added support for ECH, it means it only works within Chrome and does not extend to other apps and browsers. In contrast, AdGuard's ECH support automatically works in all apps and browsers that AdGuard filters. Therefore, you don't have to wait for operating systems or apps to support this feature, as it is automatically available in your pocket with AdGuard.

How to enable ECH support

To enable ECH support, follow these steps:

Make sure that DNS protection is on. ECH relies on data obtained through DNS, so in order for AdGuard to receive this data and enable ECH globally for users, DNS filtering is necessary.

Check if the dns.proxy.block.encrypted.client.hello.response.parameters option is turned off in the Advanced settings, as it may interfere with this feature.

Go to Advanced Settings and turn on network.https.ech.enabled.

To make sure ECH is working, use one of the following methods:

Go to https://crypto.cloudflare.com/cdn-cgi/trace/ and check if it says sni=encrypted.

Go to https://defo.ie/ech-check.php and check if it says SSL_ECH_STATUS: success.

Limitations and issues

ECH is a new technology, so you may encounter some issues when using it.

ECH support may slow down your browsing speed a bit. However, we are already working on improving this!

ECH support must be implemented on both sides. AdGuard supporting it is not enough; the server must also support it. Currently, these servers are few, because the technology is new and has not yet been finalized. However, the number of servers supporting ECH is expected to grow.

New Advanced Settings

In the Advanced settings you'll find a bunch of new features that can be divided into 4 categories:

Anti-DPI options allow low-level modification of filtering requests to protect user traffic from Deep Packet Inspection (DPI)

stealth.antidpi.clienthello.split.fragment.size

stealth.antidpi.http.space.juggling

stealth.antidpi.http.split.fragment.size

Keepalive options let you configure settings for working with Keepalive connections

network.tcp.keepalive.enabled

network.tcp.keepalive.interval.seconds

network.tcp.keepalive.timeout.seconds

DNS-related options help you fine-tune DNS settings network.https.ech.enabled

dns.proxy.fallback.on.upstreams.failure.enabled

dns.proxy.http3.enabled

dns.proxy.parallel.upstream.queries.enabled

dns.proxy.servfail.on.upstreams.failure.enabled

Certificate security options allow you to check the certificates of websites and web services by various criteria

network.https.enforce.certificate.transparency

CoreLibs, DnsLibs, Scriptlets, and ExtendedCSS have undergone many changes. Furthermore, the Ukrainian filter has been added.

Changelog

Features

DNS filtering and system DNS are enabled by default for all users #1217

Added Tor Browser support #1045

Added Arc Browser support #1188

When reporting in Safari, a new tab opens by default instead of a window #1100

Fixes

Export fails when object names contain invalid characters for a file system #1198

Network service is not connected if the app starts with Filter update check interval disabled #1190

The number of remaining days of the license period on the main screen and the License screen does not match #1177

The filtering service crashes when reading the system certificate store on MacOS 13 #1151

Versions

CoreLibs

Updated CoreLibs to v1.11.79 #1221

Encrypted ClientHello support #1565

Added exact match syntax for HTTPS exclusions #1691

Implemented "Protect from DPI" for plain HTTP #1629

Improved failure detection when starting network extension due to "no network" #1679

"Protect from DPI" allows to configure HTTPS fragmentation #1649

Added signed Certificate Timestamps (SCT) support #1529

Netbiosd process starts using a lot of CPU when pausing AdGuard #937

Fixed dropped TCP/HTTP connections #1658

Ads are not blocked by Brook #1641

Using NEAppProxyFlow.networkInterface, if installed, instead of RouteResolver #1677

Fixed incorrect work of the @match field for userscripts #1650

HTTPS filtration breaks trading.finam.ru #1724

elearning.ual.pt doesn't open with "Protect from DPI" enabled #4451

Filtering does not work on websites with dot at the end #1741

path modifier does not work on yandex.ru/images/ [#1738](https://github.com/AdguardTeam/CoreLibs/issues/1738 )

DnsLibs

Updated DnsLibs to v2.1.27 #1211

Added tplinkdeco.net to fallback domains #175

Added tplinkextender.net to fallback domains #183

Crash in IPv6-only networks on Android #182

Timing out DNS upstream leads to many requests pending #40

Scriptlets

Updated Scriptlets to v1.9.1

Added new m3u-prune scriptlet #277

Added more possible values in the set-attr scriptlet #283

Improved 'adjust-setTimeoutandadjust-setInterval` scriptlets #262

Improved json-prune scriptlet #282

Fixed compatibility for the noopcss redirect #299

Fixed compatibility issue for the google-ima redirect #272

Fixed compatibility issue between prevent-addEventListener and userscripts #271

Fixed error in prevent-element-src-loading #270

Fixed xml-prune-related errors #289

ExtendedCss

Updated ExtendedCss to v2.0.51

The content' property instyle' in IAffectedElement is now optional #163

Important for filter maintainers

Added $permissions modifier #419

Added regexp support for $domain modifier #1550

Added $url modifier #1551

Improved compatibility of $redirect syntax with uBO #1605

Improved $jsonprune #1710

$jsonprune modifier should be able to handle jsonp #1717

Send the original rule to the filtering log when applying the converted uBO-syntax HTML rule ##^script:has-text()#1709

The problem of converting HTML filtering to uBO has been solved #1708

$generichide + $generichide,badfilter causes that protection can't be enabled/disabled #1681

In some cases $important modifier doesn't work #1695

$removeparam exclusions don't work #1704

The correct rule is marked as invalid #1625

The element hiding exception doesn't work if the rule contains ~domain #1673

From this version onwards, DNS protection will be enabled by default for users who have just installed the app. When you launch the app for the first time, AdGuard uses your ISP's DNS server, but you can choose another DNS server from the list or add your own one. To do this, proceed to Settings → DNS. There you can also configure DNS filtering or turn off DNS protection.

We also updated Polish translations, fixed minor bugs and upgraded our core filtering engines – CoreLibs and DNSLibs.

Changelog

Updated

CoreLibs to v1.10.182 #1175

DnsLibs to v2.0.75 #1179

Added

PIX-LINK router/repeater domains to fallback domains #170

Missing Polish translations in Safari Browser Assistant #1174

In this version we’ve fixed some annoying bugs. Also, CoreLibs and DnsLibs have been updated, as well as DNS stamps for DNSCrypt.

Changelog

[Enhancement] CoreLibs updated to v1.10.135 #1161

[Enhancement] DnsLibs updated to v2.0.58 #1162

[Fixed] Installation issue on macOS 13 Public Beta #1116

[Fixed] Some regexp rules didn't work #1688

We are happy to present AdGuard v2.9.0 for Mac! This version delivers many changes and improvements that passed beta testing and are available to all users.

Before listing the key changes of this release, we should note that AdGuard for Mac is not supported on macOS 10.12 (Sierra) anymore. For AdGuard v2.9.0, the minimum required version of macOS is macOS 10.13 (High Sierra), and starting with the next release macOS 10.15 (Catalina) will become the lowest supported version.

[Enhancement] Implemented an option to add rules via Filtering log #925

We've implemented a long-awaited feature: now you can add rules directly from the Filtering log. Just open the Filtering log, select the query row, double-click it, press the Block or Unblock button and then select the type of rule you want to add. Finally click the Add rule button. The user rule has been added!

[Enhancement] Proxy settings moved to the Network tab #734

We've moved proxy settings from the Advanced settings, which are rarely accessed by the average user, to the Network tab in the app's Settings. Now it’s easier to set up AdGuard to connect to an outbound proxy server. By the way, you can find instructions on setting up your own proxy server and using it with AdGuard in our blog.

[Enhancement] A new Logging section added to the Advanced menu logging_item_en

Now you can select a logging level, export logs and system information, and reset logs all in one place. We'd like to remind you to switch to the Debug logging level only if our support team asks you to do so, otherwise use the Default level.

Major CoreLibs and DnsLibs update

This release contains major CoreLibs and DnsLibs updates. In CoreLibs v1.10.113 there is now an option to filter DNS-over-HTTPS, as well as support for the $jsonprune modifier. Rules with the $stealth modifier can now disable some stealth-mode options, including “Protect from DPI”. We’ve also updated the scriptlets library.

A significantly updated version of DNS filtering library DnsLibs v2.0.30 now 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 DoQ support.

Of course, besides solving global issues, we dealt with a lot of minor bugs that were preventing AdGuard from working properly. We hope you’ll enjoy AdGuard for Mac 2.9.0!

Changelog

[Enhancement] Added “Unencrypted” icon for "Regular" DNS servers description in the DNS tab #1034

[Enhancement] App exit confirmation is no longer displayed if AdGuard protection is disabled #1079

[Enhancement] Removed the word release from the number of the stable (release) version of AdGuard #1099

[Fixed] When adding a new site to the whitelist, the previously added site is removed #1056

[Fixed] Confirmation about closing AdGuard doesn't appear on top of other apps #1058

[Fixed] Error with filtering initialization through Network Extension when network is off #1124

[Fixed] Memory leaks when AdGuard is enabled #1092

[Fixed] AdGuard does not filter ad requests in sleep mode #994

Important for filter maintainers

[Enhancement] Filter metadata parsing is moved to CoreLibs

[Enhancement] Added support for editing JSON responses using $jsonprune rules #1447

[Enhancement] Added a new modifier for working with HLS (m3u8) files #1434

[Enhancement] Expanded capabilities of the $stealth modifier #1224

[Enhancement] Added support empty $path modifier for non-basic rules #1591

[Enhancement] $removeparam can be applyed to POST requests #1573

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

[Fixed] Rules with :where() pseudo class are rejected #1609

[Fixed] Fixes for preprocessor directives in filters

CoreLibs updated to v1.10.113

[Enhancement] Implemented DoH requests filtering #1563

[Enhancement] Blocker titles are discarded from the filtering lists #1667

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

[Fixed] Memory leaks when processing bypassed connections on macOS #1643

[Fixed] AdGuard for Mac blocks access to wwww.mindray.com #1648

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

[Fixed] AdGuard for Mac blocks Microsoft Edge collections #1653

[Fixed] Adguard DNS Protection doesn't support some types of system DNS servers #1061

DNSLibs updated to v2.0.30

[Fixed] Race in DNS64 discovery #1142

[Other] Added new option Block "Encrypted ClientHello" parameters to Advanced settings #161

[Other] When building projects, a warning about linking to dylib, which is not safe for use in application extensions appears #136

This is a technical update aimed to increase the app stability and fix minor bugs.

We released the last version not long ago, but it looks like we're quite the perfectionists. In the new patch, we fixed bugs with DNS filtering and small UI imperfections. And, as usual, we updated the CoreLibs and made a few more improvements to make sure it all works perfectly.

Changelog

[Enhancement] Update CoreLibs to 1.9.62

[Fixed] AdGuard sometimes crashes when importing DNS rules/domains

[Fixed] App crashes when DB malformed

[Fixed] DNS settings interface glitches when switching tabs

[Fixed] Search bar in Blocklist&Allowlist disappears

[Fixed] AdGuard does not detect the presence of a DNS profile

[Fixed] Scrollbar behavior in section “Filtered applications”

The previous release version of AdGuard for Mac came out right before Christmas, while this one comes out in time for Easter. Not that we see a trend here, just mentioning a fun fact that caught our attention. This release boasts three important features that we would like to put forward.

First off: the long-coveted settings export/import feature, that’s already been implemented in every AdGuard product but the Mac version, is here. Yes indeed, now Mac users too can finally export and import their settings in bulk, we can hardly believe it ourselves!

The second feature — now you will be seeing more dialog screens while installing. AdGuard asks a lot of permissions upon install, it is true. And it does make a lot of changes to your system configuration, more importantly it generates and installs a certificate to perform HTTPS filtering. That knowledge is enough to cause some jitters, we get that. And so it is very important for us to explain to our users that those permissions are crucial for quality filtering. Quality ad filtering is the reason behind installing AdGuard in the first place, right? In these dialog screens we state our policy: despite the permissions asked, we do not use the power gained over your system for any purpose whatsoever except filtering ads. Ever.

And last but not least, we have added an option that will hopefully improve your privacy — anti-DPI. Partially, it will prevent the Deep Packet Inspection systems of your ISP from detecting the websites you visit. This is our input in net neutrality, if you will.

These were the main points of this release, but as per usual, we also did some bug fixing (zapped a particularly odd one with the Assistant icon going grey while actually being active), and then updated CoreLibs and DNSLibs. Hope you appreciate it!

Changelog

[Enhancement] Added settings export #514

[Enhancement] Added a dialog that explains that AdGuard needs to run a rooted tool to configure the system #977

[Enhancement] Shortcuts for enabling and disabling protection #879

[Fixed] Browser Assistant icon goes gray randomly #1025

[Fixed] Do not show last updated if list does not include it #1022

[Fixed] Missing userscripts when reporting issue to AdguardFilters #1033

[Fixed] AdGuard sometimes crashes when opening AdGuard Assistant in Safari #1016

CoreLibs updated to v1.9.60

[Enhancement] Added an anti-DPI option to Stealth mode #1615

[Fixed] Kinopoisk.ru authorization failure #1502

[Fixed] Some correct rules are rejected #1531

[Other] Support for fast speeds/AdGuard locks at 300mbp/s #1561

[Other] Facebook picture upload not working #1588

[Other] DnsLibs updated to v1.7.22

Using the app has become safer, easier, and overall more pleasant. Browse the web even more securely thanks to an updated Browsing security module, activate your AdGuard account via social networks, and check for filter updates as frequently as you wish.

[Enhancement] Safebrowsing v2.0 Safebrowsing, which is responsible for blocking requests to malicious and phishing sites, has been upgraded. The new version of this module makes browsing the Internet safer than ever.

[Enhancement] Social login for license activation We’ve implemented the ability to activate AdGuard license via Google, Facebook, or Apple account.

[Enhancement] Add option to choose filters update check period #146 A long-awaited feature is finally here!

Changelog

[Added] The possibility to disable script interceptor in Advanced settings #992

[Fixed] Incompatibility with AirDrop on macOS Monterey #973

[Fixed] Issue with displaying the certificate chain through the browser assistant #836

[Fixed] AdGuard DNS crashes after waking MacBook Pro up from sleep mode #962

[Enhancement] Refined color scheme of filtering rules in Dark mode #863

[Enhancement] Started using FilterlistProcessor for downloading filter lists #995

[Enhancement] Added 360 Secure Browser to the list of filtered apps #999

[Enhancement] CoreLibs updated to 1.8.276 #1017

[Enhancement] DNSLibs updated to 1.6.71 #1011

We’re back with a patch less than a week. The apple doesn’t fall far from the tree, as the saying goes. We’re sorry for the inconvenience caused to you. This patch provides a few bug fixes and improvements. Hopefully, the new version makes things better.

[Fixed] Mail.app account switched offline #965

Sometimes traffic of non-filtered protocols in filtered apps was corrupted due to a bug. That might break IMAP connections in the Apple Mail app. As a result, users of AdGuard for Mac could not access their email accounts, they showed “Offline” in the preferences. Luckily, we managed to fix this issue at the earliest possible time, so now AdGuard users shouldn’t have any trouble with receiving emails.

Changelog

[Fixed] AdGuard DNS crashing after waking MacBook Pro up from sleep mode #962

[Enhancement] Add Sidekick to the list of default browsers #938

[Enhancement] Update CoreLibs to 1.8.221 #971

[Enhancement] Update DnsLibs to 1.6.58 #970

It took us 7 months from the previous minor release to prepare this one. Remarkably, the previous big release took place almost exactly a year ago, on October 12, 2020. That’s a substantial period of time, so we can’t help but hold our breath when we present the new version of AdGuard for Mac. It delivers such features as DNS filtering, native Apple silicon support, and Monterey support. The first two ones have been used by beta testing enthusiasts for a long time now, but today we’ve finally got to the release point, so the features will be available for all users.

DNS filtering support #685

We've used the same approach as in AdGuard for Windows, Android, and iOS, bringing to the app for Mac DNS servers, DNS blocklists and allowlists. One of feature requests from users was adding DNSCrypt, DoH, and DoT support. Finally, it's all there, DoT included. AdGuard DNS has become the first public DNS resolver to support the cutting-edge DNS-over-QUIC protocol. Now you needn't rely on a DNS server provided by your ISP by default, you can choose DNS servers from known DNS providers and add custom DNS servers. You can also add domains to DNS blocklist or allowlist and add complicated rules using DNS rules syntax. Besides, you can add DNS filters of your choice. You can find various filters and links to them here.

Native Apple Silicon support #801

Another great news is that we're added М1 support, now AdGuard for Mac is fully optimized to run on Apple Silicon.

macOS Monterey support #875

macOS Monterey is the latest version coming this fall. We did our best to make AdGuard v2.6 for Mac work seamlessly with macOS Monterey. All you need to do is wait for the newest macOS 12 to be released – to try AdGuard on it, among other things :)

Changelog

[Fixed] AdGuard no longer filters Brave Browser on Big Sur #746

[Fixed] AdGuard cannot detect that AdGuard Browser Assistant is installed in Chrome #907

[Fixed] AdGuard stops running after the Mac is out of sleep mode #781

[Fixed] AdGuard crashes when updating filters #911

[Fixed] Change the KEXT behavior in case of switching between users #769

[Fixed] Editing an allowlist causes the app to crash #860

[Fixed] Fast user switching might corrupt the certificate database #675

[Fixed] The Vivaldi Browser traffic is not filtered #852

[Fixed] AdGuard assistant: Add the ability to install in Chrome Beta/Chrome dev browser #950

[Enhancement] Update CoreLibs to 1.8.214 #960

This small update contains a CoreLibs enhancement and only one, but rather an important fix: a nasty crash that was bothering a non-zero percent of our users.

Changelog

[Enhancement] CoreLibs updated to v1.7.200 #841

[Fixed] Crash in AGNEVpnRouteResolver::refreshRoutingTable() #1416

This is a rather uncharacteristic update for AdGuard for Mac. There's no real headliner, but instead a bunch of bugfixes, low-scale improvements, and localization updates. Important! Starting with this update, AdGuard will only work on macOS 10.12+. Unfortunately, the older macOS versions do not have capabilities to support the advanced techniques we use in our filtering engine.

Changelog

[Enhancement] Update CoreLibs to 1.7.189 #835

[Fixed] Some text strings on the initial setup screen are clipped #785

[Fixed] Opera browser isn't filtered in Network extension mode #800

[Fixed] Switching between system profiles causes AdGuard to crash #805

[Fixed] hepsiburada.com - HTTPS filtering issue #1406

[Fixed] blockchain.com is broken #1411

[Other] Added Dutch localization

[Other] Microsoft Outlook removed from the list of applications filtered by default

[Other] Added AdGuard Browser Assistant extension support in Edge browser

Today we are launching a small but still very important hotfix. Namely, the compatibility with the new Chrome 87 was improved and the CoreLibs was updated.

[Other] ERR_HTTP2_PROTOCOL_ERROR on some websites #1374

This week Chrome 87 was released, which has a compatibility problem with AdGuard when using the HTTP/2 filtering protocol - some sites may experience regular hangs and download errors. In this update we have improved HTTP/2 filtering compatibility with Chrome 87, it is recommended to upgrade to the new stable version as soon as possible. :)

[Fixed] BigSur: AdGuard can't start protection in Network Extension filtering mode because of codeSignatureInvalid error

Also in this update, the issue which many Big Sur users encountered was fixed. AdGuard network extension couldn't pass the authenticity verification of the developer's signature. Because of that, it was impossible to turn the Network Extension mode on and to enable AdGuard protection.

Changelog

[Fixed] AdGuard stops working after the system is out of sleep #781

[Fixed] Change the KEXT behavior in case of a change of user #769

[Other] Protection switch is stuck after system update

[Other] Update CoreLibs to 1.7.150 #787

This patch is simple and clear: only four fixes in the main changelog and three ones in the CoreLibs section. In case you've never heard of it, CoreLibs is our filtering engine that affects filtering quality of our apps so we try to upgrade it regularly.

Changelog

[Fixed] The DeepL app won't connect #763

[Fixed] No HTTPS connectivity in browser #755

[Fixed] Nord VPN breaks connection when AdGuard uses KEXT

[Fixed] AdGuard blocks Facebook images from loading

CoreLibs updated to v1.7.143

[Fixed] $badfilter rules are sensitive to domain lists #1331

[Fixed] Issues with web filtering

[Enhancement] Improved behavior in Proxy mode when server addresses are partly unavailable #123

The biggest thing about AdGuard v2.5 for Mac is better compatibility with Big Sur. Thanks to adoption of System Extensions, AdGuard will work better on the newest macOS iteration — read below to find out the details. Other than that, we made a lot of changes and enhancements to CoreLibs, which will result in an overall better filtering quality.

[Enhancement] System Extensions support in Big Sur #692

First of all, what are System Extensions? It all started in 2019 when Apple decided to minimize the amount of code that's executed in kernel. The old framework — Kernel Extensions — was declared as deprecated. As an alternative, Apple offered System Extensions, and specifically Network Extensions as a framework for apps that filter traffic.

In macOS 11 (Big Sur), the old Kernel Extensions will not be supported (partly or at all), so we are adding support for the new framework. If you're already on Big Sur preview, make sure your AdGuard works in Network Extensions mode: open AdGuard's menu -> Select Preferences... -> Network -> Select Mode.... "Kernel Extension" mode should be grayed out, and "Network Extension" mode should be selected.

Unfortunately, as a replacement for Kernel Extensions, Network Extensions aren't around for long yet (they first appeared in this role in macOS 10.15). They are still being actively developed by Apple, so there is a significant amount of various issues associated with them. If you're facing any, please check out our problem solving guide.

Other changes

[Fixed] AdGuard icon hidden from menu bar #265

[Fixed] The protection is automatically deactivated when the system goes into sleep mode #722

[Fixed] AdGuard doesn't filter Brave Browser on Big Sur #746

[Fixed] Enable/disable protection in main menu is available when the app starts

[Fixed] Parameters stripped by Stealth Mode are not visible in filtering log

[Fixed] Incorrect behavior of EV-certs filtering feature

[Fixed] Switching between logging modes is not working with kext

[Fixed] Trackers counter doesn't work

[Other] Upstream Proxy added for AdGuard #731

[Other] Added "How to enable Network extension" screen

[Other] New app icons for Big Sur

[Other] Localizations updated

Upgraded CoreLibs to v1.7.119

[Enhancement] Add $ping content type #1258

[Enhancement] Trusted-types CSP does not break the content script #1320

[Enhancement] Indicate libraries versions #1150

[Fixed] AGFDVSocket doesn't return the original peer address in case of outbound proxy set #1330

[Fixed] AdGuard doesn't filter domains when HTTPS filtering is disabled #1343

[Fixed] Exclusion with $elemhide,jsinject,extension disable HTML filtering rules #1337

[Fixed] Filtering log doesn't show information about cookies #3406

[Fixed] Problematic userscripts #1273

[Fixed] Regexp rule doesn't match URL #1311

[Fixed] Foreign requests get into filtering log with enabled DNS module #3411

[Fixed] Path combining helper adds an extra slash #1338

[Fixed] The filter ID of the triggered rule for a blocked request is not defined correctly#1312

[Fixed] Issue with hkclubs.samsung.com #1340

[Other] Encoding errors #79

[Other] Partial HTML processing issues #1308

[Other] local.adguard.org certificate is not re-issued when it expire #1348

Here comes AdGuard for Mac 2.4! Two betas served as cornerstones for this new version and we are glad to present it to you five months after the previous release.

The biggest thing that has changed here is the new Assistant. CoreLibs has traditionally been updated, too, which enhanced filtering quality. In other aspects, 2.4 is more of a bugfix release. We cleaned it from the recurrent problems of the previous versions, polished it up, so it works nice and smooth.

[Enhancement] The old Assistant has been replaced with a native Assistant browser extension #669, #670

AdGuard Browser Assistant is a new browser extension that simultaneously takes over the roles of the old Assistant and of the integration mode. We definitely support the functional approach, so we thought: why distribute workload between two old tools when one new extension can handle it better? Now let us tell you what AdGuard Browser Assistant is capable of.

What can you do with the help of the Assistant? Enable/disable filtering on the current webpage, manually block any element on the page, reporting the website if something goes wrong or view the filtering log. Now you have all these features without the limitations that appeared in the integration mode or in the old Assistant.

When you install AdGuard for Mac for the first time (or update it to the new version), the Safari Assistant will be installed automatically. If you use another browser, you can download the Assistant at this link. Or, you can install the Assistant for your default browser via app settings or during the onboarding process.

Changelog

[Fixed] Incorrect information about QUIC connections is displayed in the filtering log #532

[Fixed] Filtering in Microsoft Edge Beta doesn't turn off when removing the browser from filtered applications #663

[Fixed] AdGuard does not preserve the Whitelist #674

[Fixed] Fast user switching might corrupt certificate database #675

[Fixed] AdGuard doesn’t work in Brave Beta 1.7.64 #689

[Enhancement] Different build configurations for beta/release/nightly #615

[Enhancement] "What's new" screen now shows up after major app updates #671

[Other] New localizations: Croatian, Persian, Romanian, Thai #678

CoreLibs has been updated to 1.5.269

[Fixed] Incorrect extended CSS rule causes problems with JS rules’ work * #1147

[Fixed] Rules with :style() are converted incorrectly #1149

[Fixed] Issue with LINE extension #1280

[Fixed] Rules with restricted domains do not match requests without referer #1286

[Fixed] Stealth mode error #1290

[Fixed] Cosmetic rules can be used as CSS rules #1293

[Fixed] Basic rules with wilcard in top level domains are not working #1298

[Enhancement] “Proceed anyway” option doesn’t work correctly if a website is blocked by a rule with $all modifier #1267

[Enhancement] New rule selection algorithm for the cases when HTTPS filtering is disabled #1291

After looking closer at the last beta we decided it was good enough to become a little proud release all by itself. It’s mostly focused on fixing network- and UI-related bugs, but there’s also a new Stealth Mode parameter to block Java.

[Added] “Block Java” option to Stealth Mode #476

[Added] HTTPS filtering step to the initial wizard #659

[Changed] Discord, Steam and Outlook added to the list of apps filtered by default #483

[Fixed] Several minor UI issues in Filters window #422

[Fixed] The text for onboarding tips is truncated in some localizations #616

[Fixed] Onboarding screen turns black #629

[Fixed] Menubar icon becomes semi-transparent #650

[Fixed] AdGuard is irresponsive after pressing "Ignore" button during settings reset #651

[Fixed] "Next" button unavailable during extension reinstall #652

[Improved] After adding a custom filter the focus is switched to that filter #441

[Improved] Certificate page design #451

[Improved] CoreLibs has been updated to v1.5.163 #662

What makes a good ad blocker update? New features? We added custom userscripts support and activation via personal account — check. Improved ad blocking quality? There’s a CoreLibs update and support for new modifiers — check. Fixes to known bugs? It’s all here, and it’s for you to enjoy!

[Added] Custom userscripts support #11

Userscripts, or “extensions” as we also call them, are highly useful mini-programs that change the behavior of web pages. Every AdGuard for Mac user probably knows about at least some of the extensions added by default, for example, AdGuard Assistant or Popup Blocker.

Now you have an option to add any custom extensions by clicking on the plus symbol in the “Extensions” tab of AdGuard settings window. You are able to load userscripts either from a local file or by URL.

[Added] Option to activate AdGuard by logging into your personal account #588

This is something we’ve already tried with some of the other AdGuard products, and it proved to be a useful addition. Basically, instead of entering a license key directly, you can link your adguard.com personal account to the app by entering the credentials, and AdGuard will automatically get activated if there’s at least one eligible license key in your account.

[Added] Scriptlets support

Scriptlets is a powerful ad blocking instrument. You can say that scriptlet is an internal script (a mini-program) that we install with the app, and then execute that script with the help of filtering rules. Putting it simply, scriptlets allow us to modify how the code of the web page behaves. As for the practical use, this helps to block anti-ad blockers, for example, and in some other cases.

[Added] $redirect and $rewrite modifiers support

They are practically the same modifiers, and they allow to substitute resources. If you are not a custom filtering rules aficionado, don't bother with it. Just know that it is yet another instrument in the hands of filter developers that helps block ads more efficiently.

We should mention that both $redirect and $rewrite modifiers are still kind of working in test mode, but they are fully operational and you should feel free to use them.

[Added] “Trusted” flag for custom filters #521

[Changed] Edge icons have been updated #641

[Changed] Opera Beta and Opera Dev added to the list of apps filtered by default #621

[Fixed] “Untrusted CA certificate” issue #596

[Fixed] Extra copies of “AdGuard Extra” userscript #607

[Fixed] Editing user rules doesn’t work when search box is not empty #569

[Fixed] AdGuard icon is invisible #527

[Fixed] Remotix compatibility issues #592

[Fixed] Custom userscripts can’t resolve URLs with non-English symbols #640

[Improved] Installer icon updated to match the app’s icons #584

[Improved] Voiceover accessibility #634

[Improved] CoreLibs has been updated to v1.5.130 #645

[Improved] AdGuard now can parse Last modified parameter of custom filters #409

[Improved] Localizations have been updated

Recently, many Chrome-based browsers have rolled out their respective updates. Due to some technical peculiarities behind these updates, AdGuard for Mac became unable to filter these browsers’ traffic. Obviously, we couldn’t sit on our hands till the next scheduled release and came up with an urgent hotfix.

This update will not blow you away, unless you are really, really into bugfixes and under the hood improvements. But those we have aplenty, especially when it comes to CoreLibs filtering engine. As a result, the new Mac version works faster and blocks ads better than its predecessor, but lacks bit in the wow-factor: the only new feature is, admittedly, rather tame.

[Added] Automatic filter subscriptions detection #279

Most filters have “subscribe” buttons on their homepages or in other places. From now on, AdGuard will be able to intercept click on such links and offer you to add these filters to the app. It’s not much perhaps, but it’s a nice thing to have and it certainly won’t hurt anyone 🙂

[Improved] CoreLibs has been updated to v1.4

There are over 50 bugfixes and improvements in this new CoreLibs version. Some notable examples:

AdGuard doesn't unnecessarily reset cookies anymore. Previously it could lead to such problems as spontaneous sign outs, which was especially irritating for websites like Twitch or YouTube.

Protection restart doesn't require closing connections anymore. Before v2.1, protection restarts could sometimes cause the interruption of your ongoing downloads, issues with online games etc.

Several issues with upload speed have been resolved.

Overall, AdGuard for Mac is now faster and much more stable than it used to be.

[Fixed] No internet connection with custom DNS in DNSCrypt #528

[Fixed] adguard-tcpkill process constantly crashes on macOS Catalina #530

[Fixed] “Reset Settings” option hangs the app #543

[Fixed] iTunes Store access issue #552

[Fixed] Compatibility issues

[Improved] Algorithm for automatic language filters activation #513

[Improved] Automatic detection of certificate issues in Firefox #472

[Improved] New settings reconfiguration method does not require closing active connections #542

[Improved] The new icon implemented across the app #561

[Improved] The protocol to add filter subscriptions #559

[Improved] Localizations has been updated

WARNING: for the app to work properly you might need to restart the system.

NOTE: if you currently have AdGuard installed to any folder except for /Applications, the old version will launch after the update anyway. In such case you need to close and uninstall the old AdGuard. Users who have AdGuard installed to /Applications already can update as usual.

Its a common situation when a release is followed by a hotfix, taking care of all unnoticed bugs. The bigger the release, the more bugfixes there usually are in the hotfix. All things considered, v2.0 can be considered a success, seeing how few serious issues we had to resolve in this update.

Ad blocking

[Fixed] Status of the "Trusted" checkbox isn't saved for custom filters #519

Network

[Fixed] Pages don't load when two system user accounts are in use #509

UI

[Fixed] Incorrect statistics after system restart #517

[Fixed] AdGuard doesn't detect some system locales #502

[Fixed] Userscripts are not translated into Traditional Chinese #503

Other

[Fixed] AdGuard installer does not work in MacOS Catalina beta #526

[Improved] CoreLibs engine has been updated #522

WARNING: for the app to work properly you might need to restart the system.

NOTE: if you currently have AdGuard installed to any folder except for /Applications, the old version will launch after the update anyway. In such case you need to close and uninstall the old AdGuard. Users who have AdGuard installed to /Applications already can update as usual.

This is one of the biggest updates in the history of AdGuard for Mac. It introduces the long-due Stealth Mode, an updated UI (including the improved Assistant), integration with CoreLibs — the new enhanced filtering engine — and much more. Give it a try and you'll immediately notice the difference.

[Added] CoreLibs integration #232

This is the first AdGuard for Mac that introduces CoreLibs — the new filtering engine that lies at the core of the filtering process. It is not random that we put this before such huge news as Stealth Mode or new design. The effects of this change will be both big and long lasting.
CoreLibs significantly enhances both ad blocking quality and performance, in comparison to the latest stable version. And since CoreLibs is a cross-platform filtering engine, in addition to these obvious improvements it allows to implement more new features that previously were only available in other AdGuard products.
Worth mentioning that AdGuard for Mac becomes the second AdGuard product to receive the «CoreLibs treatment» after AdGuard for Android.

[Added] Stealth Mode #12

Stealth Mode is a special module which sole purpose is to protect your online privacy. It went a long way from an obscure, Windows-exclusive feature, to the centerpiece of almost any AdGuard product in the very near future. This is a logical flow of things as the value of privacy has been rising to the sky for some time now, and the need to protect it becomes apparent.
If you had a chance to use AdGuard for Windows, you will find inside all familiar options. We’ll not clog up the changelog by describing every single one, they are all explained in the tooltips next to them.

[Improved] New UI #346

Finally, we get to the new UI. You may be baffled why it was left until the very end of the changelog, the explanation is very simple: the changes are modest. Both the main screen and the settings menu look different enough, but you won’t have to re-familiarize yourself with the app. Think new, prettier icons, honed styles and so on.
One thing that stands out is the new Assistant, it is miles ahead of the old version in terms of convenience, and allows you to access the web reporter for any filter-related issues on the web pages.
Oh, and another treat, exclusively for Mojave users who prefer dark themes. AdGuard now supports the dark theme, so if you switch to it in your Mac settings, AdGuard will no longer be a black sheep among your applications, pun not intended.

New users will also be greeted with redesigned onboarding screens. They are made more informative and help make first steps and adjust AdGuard according to your needs.

[Added] AdGuard Extra extension #492

In some complicated cases the usual approach with filtering rules just doesn’t work. In particular, in some cases of ad blocker circumvention/ad reinjection. So we came up with an alternative solution — a userscript. For those unfamiliar, userscripts are basically mini programs that modify web pages and augment browsing.

AdGuard Extra does it in a way that makes it harder for websites to employ the circumvention/reinjection techniques. AdGuard for Mac is the first AdGuard product to get this addition, we are thrilled to see it in action and read your feedback on it.

[Changed] Developer ID has been changed #460

Application’s Developer ID has been changed to AdGuard Software Limited. This shouldn’t concern you much, but if you are curious why it’s because of the problem we ran into on Mojave. Basically, all new and updated apps on Mojave now have to be notarized. In the future, this will be mandatory for all applications. And part of the notarization process for us was changing the Developer ID.

Ad blocking

[Added] An indicator for modified cookies in the Filtering Log #386

[Changed] Filtering rules limitations #393

[Changed] Handling of multiple $replace rules #338

[Fixed] "Proceed anyway" button does not work #369

[Fixed] "Rule" is missing from the Filtering Log item details #404

[Fixed] AdGuard crashes after editing the User filter #436

[Fixed] Compatibility problems

[Fixed] Microsoft Edge browser is not filtered #487

[Fixed] Receiving "Filter activated automatically" notification for already activated filters #366

[Fixed] Records with empty URL in the filtering log #342

[Fixed] Some filters become enabled after every app update #437

[Fixed] Vivaldi browser is not filtered #475

[Fixed] Whitelist shows comments from User Filter after update #452

Network

[Added] Stealth Mode parameters to the web reporter link #388

[Fixed] Stealth Mode actions aren't showed in the Filtering Log #355

UI

[Added] A description in the Filtering Log for some types of Stealth Mode events #421

[Added] Indicate that filter is trusted or recommended #445

[Added] New AdGuard for Mac icon #450

[Fixed] Blocked 'WebRTC, location API, push API' doesn't show in modified request in filtering log #449

[Fixed] Two notifications appear after using the manual ad blocking tool #419

Other

[Added] «Application» column to the Filtering Log #341

[Added] «Export logs and system info...» option #395

[Changed] Exception rules created via Assistant now have $document,~extension modifiers #333

[Changed] Localizations has been updated

[Changed] The list of apps filtered by default has been updated

[Changed] Users with an active subscription will not be notified anymore that their license key is soon to expire #329

[Fixed] adguard-tcpkilldoes not work with the new Chrome version #427

[Fixed] AdGuard doesn’t start automatically on the system startup #480

[Fixed] Changes to the filtered apps and extensions are not applied until the protection is restarted manually #354

[Fixed] Description for “Strip tracking parameters” option #398

[Fixed] Filtering Log issues #430

[Fixed] Forwarder applied properly to all links in the app #389

[Fixed] High CPU usage due to a sync XHR request made by the Assistant #315

[Fixed] Kext status check does not work properly on macOS 10.14 #337

[Fixed] Statistics is not counted properly #334

[Fixed] The app hanged on exit #462

[Fixed] The list of filtered apps gets reset after an update #473

[Fixed] Website report is now sent properly via the Assistant #361

[Improved] Enhanced app accessibility #406

[Improved] New onboarding screens #385, #407

[Improved] Refactoring «Launch at Login» #415

In the anticipation of the AdGuard for Mac v2.0 big update (which is coming at the beginning of the 2019 and will have loads of new features), we really want to acquaint as many people with it as possible. And the biggest driving factor here is, of course, the ability to use the product in your native language. It was nothing but unfair that we deprived our French, Danish and Norwegian-speaking users of that opportunity. We apologize and add respective localizations to AdGuard for Mac for you to enjoy. See you next year with AG for Mac v2.0!

[Changed] Localizations has been added #322

A small update for v1.5. We have temporarily disabled support for the dark theme on Mojave OS for version 1.5 since we were focused on the technical part of the development for the new version 2.0. In the upcoming major v2.0 update big changes are expected, but as for now:

[Changed] Disable dark mode on Mojave OS #379

[Changed] Localizations has been updated

[Fixed] No default filters on clean install #360

[Fixed] Welcoming UI and app menu are broken in dark mode on Mojave #359

A small but important update that resolves to issues:

[Fixed] AdGuard does not filter new Chrome 72 builds #349

[Fixed] AdGuard does not filter Brave Browser 0.55 unless you add it manually to the list of filtered apps #351

No new stunning features this time, the release is mostly about bugfixes. But they are important ones, you'll appreciate them if you were unlucky enough to come across one of the fixed issues. Oh, and we have added Japanese localization — we know there are quite a few Japanese users out there!

Networking

[Fixed] Browser connections are blocked in certain circumstances #306

[Fixed] TCP FastOpen incompatibility #309

[Fixed] Compatibility with Boxcryptor #310

[Fixed] High CPU usage due to a sync XHR request made by Assistant#315

Other

[Changed] Localization fixes for the Japanese translation #308

[Changed] Start using adguard.com/forward for the website links #313

It’s been a while since the last AdGuard for Mac release, so we owed one to our Mac users. This release is small but impactful — or at least we hope so. Some important bugfixes and key improvements have been done, all aimed at achieving better stability and filtering quality.

[Fixed] Sometimes connections can randomly slip past AdGuard #285

The title pretty much explains it. We’ve received several complaints from users about some websites not being filtered (even big ones like youtube.com). Without diving into technical details, we managed to fix it.

[Fixed] Crash in tcpClosed handler while the laptop is sleeping #295

Another bug that doesn’t really require any further explanation, but is serious enough to justify mentioning. In case you encountered this frustrating behavior — rejoice! The bug is fixed in this version.

[Improved] ExtendedCss has been updated to version 1.10 #293

This effectively means more extended cosmetic rules are supported now. Which, in its turn, ensures “cleaner” look of the post-processed pages (no ad leftovers, empty spaces etc.).

Ad blocking

[Fixed] CSP issue at github.com #292

[Fixed] HTTPS filtering + Firefox master password issue #284

Networking

[Fixed] Certain traffics gets corrupted #172

[Fixed] Dropping TCP connections leads to kernel panics after nfext unloading #276

[Fixed] AdGuard does not filter traffic when TunnelBear extension is enabled #286

UI

[Fixed] Protection status UI bug #304

[Improved] AdGuard UI files have been altered to use modern approach in localization #273

Other

[Fixed] Userscripts are injected despite being disabled #296

[Improved] Better support for language codes #290

Hello!

We are on the verge of the year 2018, and what is a better time to release a new AdGuard for Mac version? :)

As you will see with this update, a lot of major changes here relate to UI convenience and better user experience — in particular, filter subscription by URL deserves a separate mention. Ad blocking quality has been increased too, several bugs have been eliminated.

Ad blocking

[Added] Filter subscription by URL #1

It’s become much more convenient now to add new filter subscriptions since you have a choice between uploading a local file or entering a URL.

[Improved] Close active connections when network filtering starts #263

Translating to a more common language, this means that no connections will slip by AdGuard’s protection when you turn it on. A real life example: many Safari users used to have problems with unblocked ads on YouTube. This change fixes it. - [Added] $~websocket modifier support #245

[Added] "Brave" browser to the filtered apps list #246

[Added] Mozilla Developer Edition to the filtered apps list #241

[Fixed] Can't log in to icloud.com #242

[Fixed] AdGuard blocks notifications on Yandex mail in a browser tab #256

[Fixed] "Reinstall certificate" does not work in FF #257

[Fixed] Some websites open slowly with AdGuard #247

[Fixed] Some websites are not accessible with the HTTPS filtering enabled #249

UI

[Added] "Undo/Redo" buttons to the user filter editor #227

Self-explanatory. Working with filter editor has become so much more convenient — trust us, we do it a lot, and we can tell the difference! [Improved] Filter editor now indicates that the filter contains disabled rules #258

Another quality of life improvement. You won’t now find yourself in situations when something is not working because you’ve disabled a couple of rules, but can’t remember in what filter. - [Added] Inform the user about closed connection to a website with EV certificate #228

[Fixed] Applied settings are not displayed correctly when the language filters are activated automatically #233

[Fixed] No first run wizard when installing on High Sierra #244

[Fixed] Title of the window appears on wizard style windows on MacOS 10.13 #255

Other

[Fixed] "Shadowsocks-R" and AdGuard compatibility problem #240

[Improved] "ExtendedCss" module has been upgraded to v1.0.9 #262

[Fixed] Localization issues #261

It has been a very long time since the last AdGuard for Mac release. We definitely don't want such hiatus to become a routine – expect the next one much sooner.

And in this one we've made some positive changes to the UI and improved the filtering quality by a lot. Read the full changelog below.

Ad blocking

[Fixed] AdGuard doesn't filter apps from the WebCatalog app #165

Previously, AdGuard wasn’t able to filter apps installed with WebCatalog, and they couldn’t even be added to the list of filtered apps manually. This issue gets fixed in this version. - [Added] $network basic rules modifier #171

[Changed] The ~third-party modifier behavior #177

[Fixed] Content filtering exception rules #176

[Fixed] Error while parsing a wide filtering rule #175

[Fixed] Replace rules aren't applied to .m3u8 files content #178

[Fixed] Regular expressions with $ aren't processed properly #167

[Fixed] Content rules are applied even when there is a $document exception #234

[Fixed[ The script is being removed/cut if there is an $empty modifier in the rule #209

[Fixed] Cosmetic filters are being applied to pages whitelisted by a $document exception #189

[Improved] The range of $$ rules has been increased #196

[Improved] "ExtendedCss" module has been upgraded to v1.0.8 #216

[Improved] The trimming limit for request URLs has been increased #214

[Improved] The $network modifier has been extended, it can now be an exception as well #190

Networking

[Added] An option to exclude websites with EV certificates from filtering #170

An option already familiar to Windows users. Some websites feature Extended Validation (EV) SSL certificates, which require a very strict verification process and offer a stronger guarantee that the website is plausible and trusted. Usually, they are bank websites, payment systems etc., and they normally do not have many ads anyway, if any.

We have also improved the security aspect of AdGuard by addressing some security-related issues (#186, #194).

[Fixed] Wrong cyphers order #224

[Fixed] SHA-1 intermediate issue #194

[Fixed] AdGuard cannot handle huge chunks properly #218

[Fixed] Connection is allowed when DH1024 is in use #186

[Fixed] "strict-dynamic" CSP is not handled properly #203

[Fixed] AdGuard Crashes when receives new metadata from backend #220

[Fixed] There is an empty response from local.adguard.com in some cases when HTTPS is used #206

[Fixed] Several network errors and compatibility issues

UI

[Improved] Filter editor has been reworked #56

Now it has become possible to enter the 'advanced editing mode'. Basically, it means that the User filter turns into a single text area which you can work with as in any text editor: copy/paste several lines at once and apply all changes at once and not line by line. The search tool will help you to find or replace anything you need. All in all, it should be a welcome change for all the aspiring filter developers.

[Added] Add "Reset settings..." option #180

[Changed] "System Extension Blocked" issue on macOS 10.13 (High Sierra) #217

[Changed] Filters' names have been adjusted #187

[Changed] AdGuard to AdGuard #231

[Fixed] Wrong date of establishment in "About AdGuard" section #205

[Fixed] Several localization fixes and updates

[Fixed] The 'expiring trial' warning translation #169

[Fixed] The number of remaining subscription days is not displayed in AdGuard toolbar #191

[Fixed] UF is always turned on after restarting the app #237

[Fixed] Interface bug with filters list #236

[Fixed] Misplaced title in Support window #235

Other

[Improved] AdGuard can now be launched from an external drive #210

A niche but useful improvement. In case you prefer to store your data on an external drive and switch between different desktops a lot. No need to update your user filter and other settings separately on every Mac separately anymore, just have AdGuard installed on an external drive.

[Changed] The SSL exceptions list has been updated

[Fixed] Yandex mail compatibility issue #160

IMPORTANT UPDATE: compatibility with Chrome 59 and newer. The changes are few, but crucial.

[Fixed] local.adguard.com certificate is considered invalid by Chrome v59 #183

It may not seem like much, but without this change, AdGuard would be partially incompatible with the newest Chrome versions. Needless to say, Chrome is one of the most popular browsers among Mac users, so it is hard to overstate the importance of this fix.

[Changed] Bundle ID for Waterfox app #164

A small hotfix containing a couple of changes.

[Fixed] AdGuard maintains network connections even if the computer is in idle mode #163

[Improved] Cosmetic exception rules compilation speed #173

The Christmas came early this year for AdGuard for Mac users - a new version comes out today :) It significantly improves ad blocking, namely introducing Extended CSS support and several new modifiers. Networking and UI have undergone some fixing and tweaking too, so AdGuard will become more stable and easy in use.

Ad blocking

[Added] Extended CSS support #109, #120
This is a very important addition in terms of future (and present) possibilities that it opens for ad blocking. Extended CSS is a module for applying CSS styles with extended selection properties. Basically, it means that we will be able to select and, therefore, block some elements that we would not be able to block otherwise. Notably, this concerns such things as 'Sponsored posts' on Facebook.

[Added] $important modifier #132
This new addition is an significant one, but mostly relevant for creators of custom filter rules. With it's help you can give certain rules higher priority.

[Added] $websocket modifier #131

[Changed] Updated default HTTPS exclusions list #124

[Fixed] $empty modifier behaviour #108, #143

[Fixed] Latin extended symbol in a filter rule interferes with filtering #134

[Fixed] $replace rule can't be applied along with the other rules #133

Networking

[Changed] HTTPS is now used for safebrowsing requests #148

[Changed] WoSign and StartCom certificates are now distrusted #141

[Changed] New separate server is used now for filter updates #139

[Fixed] $replace rules break content charset #147

[Fixed] AdGuard compatibility with Opera built-in VPN #123, #130

[Fixed] Kernel panic issue #106

[Fixed] AdGuard blocks the page from loading if /etc/hosts has incorrect records #111

[Fixed] Inability to apply inline style #142

[Fixed] Excessive CPU load #135

[Fixed] Safebrowsing check algorithm #148

[Fixed] Unknown pseudo class error #154

[Improved] Content injection algorithm #119

[Improved] AdGuard styles are now protected from removal #149

UI

[Added] Hotkeys for filters management #9, #128

[Changed] CMD+Backspace key combination can now be used to delete filters from the filter list #9

[Changed] "Check filter updates" action moved to settings menu #116

[Fixed] Incorrect filter is displayed in "Filtering Log" #129

[Fixed] $replace rules are displayed correctly in the filtering log #150

[Improved] Allowed pasting mulitple rules at once in filter area #126

Hello! Last AdGuard for Mac version was released in February, so we felt a bit guilty and decided to release a new one :) There is quite a bit of various fixes and changes here, as you can see in the changelog below, but the most important, or rather the most impactful ones, are those that affect performance - specifically, we mean #88 and #91 (you can find more detailed description for these changes below). Overall, AdGuard will become faster now, and thanks to the better performance, AdGuard will now consume significantly less battery resourse. But not only that, for example, we drastically improved browsing of some of the most problematic websites when IPv6 is enabled (#93).

Ad blocking

[Improved] Basic filtering rules processing speed was optimized #91

Optimizing basic filtering rules processing is very important since basic rules are the most resourse-consuming among all. This change will result in AdGuard working faster and spending less resourses.

[Changed] $replace rules now have higher priority than other basic rules #49

[Changed] Origin is used as Referer for requests Referer isn't defined for #84

[Fixed] AdGuard crash because of huge data: URLs #81

[Fixed] AdGuard does not ignore "base" tag "href " attribute while constructing absolute URL any more #80

[Fixed] Websites can't be broken any more because of invalid HTML inside a "noscript" tag #79

[Fixed] Error previously occuring when parsing a style tag with embedded svg #76

[Fixed] AdGuard can now detect HTML if there is an xml declaration at the document start #83

[Fixed] Wrong HTML content detection #71

[Fixed] twitch.tv filtering issue #105

[Improved] Increase content filtering rules maximum length limit #101

Networking

[Changed] Connections are not kept alive for too long now if 'HTTP keep alive' timeout is specified #88

Previously the 'keep-alive' time for connections was higher, and AdGuard consumed more battery resourse than it should. Now, when we lowered the connections 'keep-alive' time, the resourse consumption during the 'idle time' will be significantly lower as well.

[Changed] Webdav methods are supported now (specifically REPORT) #85

[Changed] Rewritten mechanism of checking the websites availability #93

[Fixed] After blocking a POST request, next request is read only when data was read to end #68

[Fixed] AdGuard prevents UDP traffic on 443 port #90

[Fixed] AdGuard fails to detect HTML on some websites #100

UI changes

[Added] A notification that is shown if user unchecks the "Filter https protocol" box #65

Languages and Translations

[Added] Finnish language #63

Minor issues

[Added] Support for complex language codes #78

[Changed] Increase idle connection timeout to 10 minutes #102

[Fixed] Problem with AdGuard start after motherboard replacement #77

[Fixed] Wrong information in AdGuard's filtering log #75

[Fixed] Added description of the status code in filtered HTTP response #74

[Fixed] Spelling issue #73

[Fixed] Occasional app crash when user attempts to view AdGuard Program Log #66

[Fixed] Apps crash #67

[Fixed] AdGuards code is no more injected into noscript tag #64

[Fixed] Major battery resourse consumption on Mac #52

This new version brings a lot of very important changes to AdGuard for Mac. Most viable changes are: $replace modifier and security improvements.

UI changes

[Added] New localizations: Serbian (Latin), German, Italian, Spanish, Chinese Traditional, Armenian, Turkish, Korean, Indonesian, Hungarian. #50

[Added] User warnings in case HTTP proxy mode fails to start. #22

[Changed] Assistant requests are now excluded from 'Filtering log'. #4

[Changed] Now clicking on AdGuard icon in status bar brings opened AdGuard windows to front and makes them active. #33

[Fixed] Error previously led to inability to change HTTP proxy port with HTTP proxy mode enabled. #42

[Fixed] Lack of explanation text in the 'Enter email address' text field. #44

Ad blocking

[Added] $genericblock rule modifier. #16

[Added] $generichide rule modifier. #15

[Added] $replace modifier for basic rules #38

[Changed] Now $popup rules modifier is also applied to server redirect responses. #49

[Changed] Now status 500 is always returned for blocked requests. #35

[Changed] User filter is now loaded last, after all other filters are loaded. #41

[Fixed] Error in css-inject rules. #7

[Fixed] Error in finding the elements path on a page for HTML filtering rules. #17

[Fixed] Error in HTML filtering rules – previously empty elements were never removed. #29

[Fixed] Improved processing of rules with $popup modifier. #25

[Fixed] Modifiers for the whitelist rules now work while filtering content. #57

[Fixed] Now $elemhide rule modifier is applied only to HTML pages. #14

[Fixed] Problem with basic rules being treated as rules with $popup modifier. #34

[Fixed] Template modifier * in rules now takes into account line break symbols. #40

[Fixed] Third-party requests filtering error. #6

Networking

[Changed] AdGuard automatically stops filtering of the websites with client certificate authorization. #2

[Changed] Browser cache is now suppressed for a short period of time after filtering startup. #53

[Changed] For all modern browsers SHA1 certificates were deprecated. #46

[Changed] Port AdGuard accepts connections on. #5

[Changed] Updated default list of SSL exceptions. #3

[Fixed] Problem when AdGuard caused browser to freeze. #37

Browsing Security

[Changed] A method of domain check with Browsing Security module. Requests privacy was improved. #8

Compatibility issues

[Improved] Compatibility with sites that use the Content-Security-Policy mechanism. #58

[Fixed] Blocking of Google Chrome Rapportive extension for Gmail. #30

[Fixed] Problem when AdGuard extension for Google Chrome couldn't see triggered $genericblock rules. Integration mode works correctly now. #39

[Fixed] Safari inability to connect to some websites with IPv6 network configuration. #10

Added function to send a report in case of an unexpected AdGuard shutdown.

Added tutorial screen at AdGuard first launch.

Added OCSP Stapling support.

Added localizations: Chinese (Simplified), Polish, Portuguese (Brazil), Slovak, Korean.

Changed SSL connections encrypting mode to a more modern one.

Improved root certificate and private key generation for SSL connections.

Fixed Logjam vulnerability (now AdGuard doesn't filter connections with weak keys).

Improved mechanism of SSL connections processing.

Significantly extended list of browsers filtered by default.

Now, in case of its absence, AdGuard automatically suggests to install root certificate into Firefox to filter HTTPS-websites.

Improved way of root certificate installation into Mozilla-based browsers.

Improved security of installing AdGuard Assistant to web pages.

Improved AdGuard API extensions security.

Confined access to userscripts API functions.

Reworked installation process, now AdGuard will work correctly after restoring Mac from Time Machine.

Improved filtering rules correctness verification.

Now AdGuard system components are stored in the folder shared for all users.

Now upon switching Mac to sleep mode, AdGuard closes current network connections.

Fixed situation when AdGuard won't respond to users actions while watching a video on YouTube.

Fixed error previously led to AdGuard crash while surfing a website with incorrect HTML.

Fixed an error previously led to rules with specific symbols being excluded from filtering process.

Fixed an error previously led to shutdown when exiting AdGuard.

Added TLSv1.2 support.

Added certificate verification in HTTPS connections.

Added Ukrainian localization.

Chromium added to default application filtering list.

Now automatic check for updates is enabled by default.

Improved speed optimization.

Removed splashscreen upon starting AdGuard.

Fixed AdGuard's work with several users on the same computer.

Fixed errors leading to incorrect filtering.

Fixed the error when AdGuard operated incorrectly upon exiting sleep mode.

Improved security upon filtering encrypted traffic.

Fixed FREAK vulnerability.

Fixed memory leaks.

Improved program stability on old versions of OS X.

Fixed several errors that could previously lead to app crash.

World’s first standalone ad blocker for Mac OS X. New AdGuard has all the features to ensure more efficient and comfortable use of the Internet:

Ad filtering in any browser. Our ad blocker is the first to solve the problem of removing notorious video ads in Safari that other adblock solutions fail to block.

Built-in Browsing security module provides protection from malicious and suspicious websites.

Privacy protection function is responsible for the safety of personal data.

Other advantages

Filtering Log demonstrates all the processes occurring in the program.

AdGuard Assistant is an extension that allows you to manage the program directly from the browser.

Technical information

AdGuard is supported in all versions of OS X from 10.7 and later.

AdGuard for Mac – Release – AdGuard versions

Faster filter lists update

Customized browsing

Changelog

Improvements

Fixes

DnsLibs (DNS filtering engine)

CoreLibs (Filtering engine)

Improvements

Fixes

Scriptlets (JavaScript enhancement for filtering rules)

Improvements

Fixes

Changelog

Improvements

Fixes

CoreLibs (filtering engine)

Improvements

Fixes

UserscriptsWrapper

Fixes

ContentScript

Fixes

DnsLibs (DNS filtering engine)

Changelog

Fixes

CoreLibs (Filtering engine)

DnsLibs (DNS filtering engine)

Changelog

Fixes

CoreLibs (Filtering engine) updated to v1.14.51

Improvements

Fixes

Other

DnsLibs (DNS filtering engine) updated to v2.5.18

Improvements

Other

UserscriptsWrapper updated to v1.2.23

Scriptlets (JavaScript enhancement for filtering rules) updated to v1.10.25

Improvements

Fixes

More transparency to HTTPS filtering

Support for selectors in HTML filtering rules

New DnsLibs and Basic HTTP authentication

Changelog

Improvements

Fixes

CoreLibs (Filtering engine)

Improvements

Fixes

DnsLibs (DNS filtering engine)

Fixes

Important for filter maintainers

Scriptlets (JavaScript enhancement for filtering rules)​

Improvements​

Fixes

UserscriptsWrapper​

Changelog

Fixes

CoreLibs (Filtering engine)

Changelog

Fixes

CoreLibs

DnsLibs

Changelog

Features

Fixes

Important for filter maintainers

Features

Fixes

Scriptlets

Scriptlets updated to v1.9.62

Features

Fixes

Versions

CoreLibs

Features

Fixes

DnsLibs

Features

Scriptlets (JavaScript enhancement for filtering rules)

Improvements

UserscriptsWrapper