版本歷史 | AdGuard

“親愛的開發人員，可以修復一個錯誤嗎？” 當然可以！隨著更新發佈，我們還推出帶有已解決問題和微調操作的修復程式。

有沒有使用者曾經分享過設定？該功能特別適用於不想在新裝置上重新配置全部設定，或是想報告錯過的廣告的情況。在新版本中，共享設定變得更加便捷簡單：要匯出設定，進入「設定」→「高級」→「共享設定...」，要匯入設定，只需在瀏覽器中開啟生成的連結並點選「匯入」即可。

我們還更新了 CoreLibs 過濾引擎，崩潰次數將減少，修飾符數量將增加，包括 $xmlprune 和 $urltransform 修飾符。現在，使用者可以封鎖更多幹擾頁面的元件。

更新記錄

改進

在 macOS 上應用通過 URL 匯入配置的功能 #1428

修復

macOS Big Sur 上的 Safari 助理缺少「開啟設定」按鈕文本 #1366

CoreLibs（過濾引擎）

將 CoreLibs 更新為 v1.15.64 #1456

改進

新增了 $urltransform （可信任的）修飾符 #1364

新增了 $xmlprune 修飾符 #473

在本機支援 ':has()' 的使用者代理清單中新增了行動瀏覽器 #1870

本機 sid 上允許 ECDSA 密碼 #360

設定 Sec-Fetch-Dest: fencedframe #1853

新增 uBO 的 /regex/ 格式（修飾規則）的支援 #1844

修復

啟用 VPN 後，AdGuard 過濾停止工作 #1189

帶有 FQDN 的 Adblock 語法規則不起作用 #210

AdGuard 和 FTP 連線錯誤 #1864

使用者腳本 XHR 錯誤 #1876

$all 修飾符不適用於非域名 URL 的部分 #1860

URL 阻止規則在使用 $generichide 修飾符時無法正常工作 #1857

UserscriptsWrapper

將 UserscriptsWrapper 更新為 v1.2.24

修復

vk-metabot.user.js 無法與 AdGuard 一起使用 #1871

ContentScript

將 ContentScript 更新為 v2.0.6

修復

元件隱藏規則 ## 和 #$# 不適用於 tv.ramler.ru #1865

DnsLibs（DNS 過濾引擎）

將 DnsLibs 更新為 v2.5.34 #1436

這次技術更新，我們提高了應用程式的穩定性並修復了一些程式錯誤。

有些使用者遇到 AdGuard 導致 CPU 使用率過高的問題。我們在此修補程式中修復了這一問題，並更新了 CoreLibs 和 DnsLibs。

更新記錄

修復

CPU 使用率過高 #1407

CoreLibs (Filtering engine)

將 CoreLibs 更新為 v1.14.57 #1423

DnsLibs (DNS filtering engine)

將 DnsLibs 更新為 v2.5.25 #1421

AdGuard v2.14 Mac 版修復了常見錯誤，提高了性能，但不僅如此！這次的主角是 CoreLibs 更新。本次更新對應用程式整體進行了大升級，尤其是在兩方面上。第一個方面是，我們對 Encrypted ClientHello 支援進行了微調。雖然這一功能仍處於試驗階段，但我們已經發現了幾個阻礙預設啟用模式下無縫啟動 ECH 的問題。通過這次發佈，我們已經解決了這些問題，為提高總體性能鋪平了道路。此外，更新後的 CoreLibs 現在還能即時過濾 DNS-over-HTTPS 請求。這意味著 AdGuard 預設不會將 DoH 查詢重新導向另一個 DNS 伺服器，而是將查詢傳送到瀏覽器中選擇的伺服器上。可以通過關閉進階設定中的 network.dns.filter.secure.request.transparently.enabled 來恢復舊的設定。本次更新還包括其他小改進和錯誤修復。如果您想了解更多，請閱讀我們的更新記錄。

更新記錄

修復

「代理配置」上的按鈕在某些情況下沒有反應 #1327

將 CoreLibs （過濾引擎）更新為 v1.14.51

改進

在請求已處理事件中指示是否使用了往外代理 #1385

新增將主機傳遞給往外代理的支援 #1386

改進了使用者規則編輯器 #1402

修復

僅對 document 套用 $permissions #1856

無法將 QUIC ClientHello 解析分成兩個數據包 #1861

名稱中包含 [ and ] 的 Cookie 規則被視為無效 #1843

同時運行 AdGuard 和 AdGuard VPN 瀏覽器擴充功能時，在某些情況下無法套用修飾符規則 #1791

VOT（嗓音起始時間）腳本無法在 Google 瀏覽器中運行 #1665

$all 修飾符工作不正確 #1842

未註入 mall.sk 內容腳本 #1834

其他

在本機支援 :has() 的使用者代理清單中新增 Firefox 121.0+ #1840

在 $permissions 中新增了使用 | 作為分隔符的選項 #1850

在字符類中封鎖帶有轉義斜線的 regex 規則不起作用 #1831

如果在 doctype 宣告之前有標記（帶 embed 屬性），則無法註入內容腳本 #1825

新增了截獲 DNS HTTPS 查詢中的 ECH 參數 #1794

改進 HTML 過濾性能 #1855

DoH 連線的 on-the-fly 過濾支援 #198

支援韓國電信的反 DPI 功能 #1789

$path 修飾符對查詢參數不起作用 #1817

有端口的 URL 上的 $removeparam 重新導向無端口的 URL #1818

AdGuard 破解 android-hilfe.de 網站 #1800

無法安全連線到 wiki.cemu.info #1821

將 DnsLibs（DNS 過濾引擎）更新為 v2.5.18

改進

允許指定僅 tcp 和僅 udp DNS 上遊 #208

支援嚮出站代理傳遞主機名，而不是引導 #197

其他

改進對 HTTPS rrtype 的處理 #215

使用 DoH 中 IPv4/IPv6 的 Happy Eyeballs #217

UserscriptsWrapper 更新為 v1.2.23

將 Scriptlets（過濾規則的 JavaScript 改進）更新為 v1.10.25

新增 GM.xmlhttpRequest 作為 GM_xmlhttpRequest 的別名 #1785

改進

新增與 uBO 的 set-cookie 腳本程式的相容性 #332

新增新腳本程式 call-nothrow.js #333

新增新腳本程式 spoof-css #317

新增新腳本 trusted-create-element #278

新增更多支援值改進了 set-cookie #379

新增 ga.q 屬性改進了 Google 分析功能 #355

新增 OmidVerificationVendor 屬性改進了 google-ima3 #353

新增新腳本 href-sanitizer #327

新增新腳本 json-prune-fetch-response #361

新增新腳本 json-prune-xhr-response #360

新增新腳本 trusted-suppress-native-method #383

set-cookie，增加一個可能的數值 #388

trusted-click-element，添加在 shadowRoot 中查找選擇器的支援 #323

將一些重定嚮資源也用作小腳本 #300

新腳本 trusted-set-attr #281

新腳本 no-protected-audience #395

增加了允許清單腳本的選擇 #377

改進的 prevent-fetch，新增 cors 回響類型 #394

改進的 set-cookie，新增「域名」參數 #389

修復

set-constant — setProxyTrap() #403

set-cookie — 不進行 Cookie 名稱編碼 #408

set-local-storage-item 轉換 — '$remove$' 參數 #404

我們非常高興地宣佈 Mac 版 AdGuard v2.13 的新版本。該版本包含多項底層改進和錯誤修復，可大大增強使用者的瀏覽體驗。此外，我們還在 AdGuard 引入了一些新的實用功能，提高了廣告封鎖的效率。讓我們仔細看看主要的改進。

提高 HTTPS 過濾的透明度

為了提高 HTTPS 過濾的透明度，AdGuard 提供通過「過濾記錄」檢查原始憑證的選項。現在，使用者可以查看任何網路請求的詳細資訊，檢查 AdGuard 使用的加密，並檢查原始憑證。

此功能源於 HTTPS 過濾的一個主要問題。AdGuard 能有效地驗證憑證，但在某些情況下，使用者可能希望自己檢查原始憑證。您可以在我們的知識庫中閱讀有關此問題的更多資訊。

HTML 過濾規則選擇器的支援

該版本的最大變化是改進 HTML 過濾功能。AdGuard 在 HTML 過濾規則中新增了對選擇器的支援，這有助於更有效地封鎖廣告。

新 DnsLibs 和基本 HTTP 驗證

通過此次 DnsLibs 更新，AdGuard Mac 版的使用者可以使用一項新功能，即「基本 HTTP 身份驗證」。這意味著什麼？

假設使用者有一個自訂的 DNS 伺服器，並希望限制對它的存取權限。使用者可以通過 IP 位址來限制存取權限（例如，只允許家庭 IP 連線到 DNS 伺服器），但如果行動裝置經常更換網路怎麼辦？

好消息，DNS-over-HTTPS 協定可以讓我們享受 HTTP 協定的各種好處，其中之一就是身份驗證選項。現在，在 AdGuard Mac 版中新增支援 HTTP 身份驗證的自訂的 DNS 伺服器時，可以包含用於連線到該伺服器的身份驗證資訊。

很快，AdGuard Home 和 AdGuard DNS 將提供「基本 HTTP 身份驗證」，敬請期待！

我們還修復了一些小錯誤，並提高了 AdGuard 的性能和穩定性。希望您會喜歡 AdGuard v2.13 Mac 版。

更新記錄

改進

為 AdGuard 助理新增了 Vivaldi 支援 #998

在過濾記錄中顯示 HTTPS 過濾狀態和原始憑證 #1284

修復

停止/啟動 DNS 服務失敗 #1311

在 AdGuard 運行的情況下，WARP 收到「無法連線」錯誤資訊 #1234

開啟 AdGuard 時，Wi-Fi 授權彈出式窗口不顯示 #892

DNS 過濾破壞 Tunnelblick VPN #1310

CoreLibs（過濾引起）

將 CoreLibs 更新為 v1.13.115

刪除了行動憑證的選項 #277

為韓國電信新增了反 DPI 功能支援 #1789

改進

已新增 !#else 預處理器指令支援 #1806

採用新的規則優先權方案 #1768

更改了 sec-ch-ua 標頭，以在啟用隱匿模式時匹配使用者代理 #1764

改進 HTML 過濾性能 #1772

改進了 ECH retry_configs 的用法 #1793

修復

在 Edge Bing Chat 中不顯示圖片 #1744

使用 SXG 的網站從 Google 搜尋開啟時沒有修飾過濾功能 #1812

macperformanceguide.com 網站上的過濾功能不起作用 #1810

TCP/IP 協定棧中的 UDP 超時太短 #1796

由於網站憑證不同，其中一個子域未被過濾 #1839

DnsLibs（DNS 過濾引擎）

將 DnsLibs 更新為 v2.4.36

#### 改進

為 DoH 端點新增了基本驗證功能 #189

允許在精確域名規則中使用 # 註釋 #196

修復

本地 DNS 代理在使用普通 DNS 上遊時可能受到 DoS 攻擊 #202

DoH 試圖用陳舊的連線，時間太長了 #200

正確過濾 type=HTTPS 請求 #199

過濾器改進

新增了 $extension 修飾符 disabling specific userscript #1706

改進了 HTML 過濾規則 $$，允許 CSS 的選擇器 #94

新增了 cap_html_filtering 狀態的支援 #1758

$denyallow 不允許封鎖檔案 #1809

$stealth 例外在 TCP 棧層不起作用，我們在此阻止 STUN/TURN #1737

未將內容腳本註入 object 標記中加載的元素 #1769

根據 HTML "lang" 屬性和語言請求 HTTP 頭信息檢測網站的地域 #1736

$replace, $hls 和 $jsonprune 的回復大小限制提高到 10MB #326

Scriptlets（過濾規則的 JavaScript 改善）

* 將 Scriptlets 更新為 v1.9.101

改進

改進 prevent-fetch #364

改進了儲存項目腳本，為刪除項目新增 regexp 支援 #256

新增了新的受信任腳本 trusted-prune-inbound-object #372

為 set-cookie 新增了更多支援值 #375

改進了 set-local-storage-item 和 set-session-storage-item，增加了對「開」和「關」的支援 #366

處理 uBO 的語法 $redirect 優先級 #59

改進了 xml-prune，支援 xpath 文本內容匹配 #325

新增了根據名稱轉換重新導向的 API 方法 #346

改進了 json-prune 的 stack 工作 #348

改進的 prevent-xhr #347

修復

googletagservices-gpt 缺少 setPrivacySettings 方法 #344

set-constant 腳本小程式突破 vimeo.com #380

修正了超出最大調用堆棧大小時的 set-constant 腳本程式 #373

修正了 set-constant 值的問題 #330

修復了 music.youtube.com 上的 trusted-replace-xhr-response 錯誤 #359

改進了 m3u-prune，如果存在 \r 則不會裁剪內容 #354

改進了 trusted-replace-fetch-response，如果 URL 由 Object.defineProperty 設定，則不替換內容 #367

在將參數轉換為 uBO 規則時，參數中的逗號被刪除 #343

UserscriptsWrapper

將 UserscriptsWrapper 更新為 v1.2.21

网盘直链下载助手 使用者腳本無法與 AdGuard 運行 #1780

我們發佈了 Mac 版的更新！在 AdGuard v2.12.2 Mac 版中，我們解決了影響 Firefox 使用者的一個嚴重問題。啟用 AdGuard 後，某些網站無法載入，並會顯示與安全憑證有關的錯誤。

更新記錄

修復

Firefox 中的 HSTS/SSL 錯誤 #1326

CoreLibs（過濾引擎）

將 CoreLibs 更新為 v1.12.83 #1324

在以前的 AdGuard Mac 版本中，有些使用者遇到了一個問題，即每次系統重啟後都會出現「AdGuard 要進行變更」的提示。在 AdGuard v2.12.1 Mac 版中，我們修復了這個錯誤，並更新了 CoreLibs 和 DnsLibs。

更新記錄

修復

AdGuard 重啟後不斷要求輸入管理員密碼 #1307

在 'have-result' 狀態下，連線超時 #1180

使用 127.0.0.1 local 規則時，AdGuard 會阻止對 .local 域名的所有請求 #207

CoreLibs

將 CoreLibs 更新為 v1.12.78 #1308

DnsLibs

將 DnsLibs 更新為 v2.2.36 #1314

我們很高興地宣布 Mac 版 AdGuard v2.12 已經更新了！這次我們大大改進了使用者體驗和隱私保護水平。請注意，此版本不再支援 macOS High Sierra 10.13 和 Mojave 10.14。如果有使用者目前在使用舊版本的 Mac，請下載 AdGuard 的舊版本。

Mac 版 AdGuard v2.12 推出重大改進。之前，軟體只能過濾 HTTP/1 和 HTTP/2 流量。在 v2.12 中，我們更新了 CoreLibs，讓使用者可以啟用 HTTP/3 過濾。HTTP/3（HTTP-over-QUIC）是HTTP 協定的最新版本，使用 QUIC 代替 TCP 。與 TCP 傳輸層協定相比，QUIC 網路協定有很多優點。它能提高隱私性和安全性，提供更穩定、更快速的網際網路連線等優點。啟用 HTTP/3 過濾後，使用者不僅可以使用 QUIC 協定的所有優點，還可以封鎖廣告和追蹤器！現在，我們的使用者可以不受任何幹擾地享受快速的網際網路連線。

目前，HTTP/3 過濾是一項實驗性功能。此外，由於瀏覽器特定錯誤，該功能在 Chrome 瀏覽器中已經失效。不過，在 Safari 和 Firefox 中應該可以正常使用。要使用 HTTP/3 過濾，請轉到「高級」→ 「高級設定」→「network.https.filter.http3.enabled」。

我們還修復了與 WARP 的相容問題，更新了 Scriptlets、CoreLibs 和 DnsLibs。

更新記錄

功能

實驗性 HTTP/3 過濾的支援 #1253

修復

AdGuard 預設無法封鎖 macOS Sonoma 上 "Web Apps" 中的廣告 #1292

將滑鼠懸停在更新按鈕上時，指針不會改變 #1244

應用程式只安裝了一個非推薦的惱人的事物過濾器，而不是 5 個推薦過濾器 #1263

過濾器的改進

功能

為基本規則新增了 $method 修飾#1713

允許使用空模式的 $stealth 規則 #1762

修復

$jsonprune、$replace、$hls不適用於 non-GET-POST HTTP 方法 #1743

$path修飾在路徑market.yandex.ru/?` 上不起作用 #1726

$jsonprune 修飾應能處理 jsonp 的引號 #1734

$network` 規則在帶有 kext 的 macOS 上不起作用 #1773

如果 ExtendedCss 的使用不受限於 #?# 規則標記，可將 :has()、:not()、:is() 視為標準偽類 #1683

Scriptlets

將 Scriptlets 更新為 v1.9.62

功能

新增了根據名稱轉換重新導向的 API 方法 #346

改進了 trusted-replace-fetch-response/trusted-replace-xhr-response，增加了替換所有匹配內容的功能 #303

新增了新 evaldata-prune scriptlet #322

新增了新 remove-node-text scriptlets #318

新增了新 trusted-replace-node-text scriptlet #319

修復

新增了返回 set-constant scriptlet 支援值的新方法 #316

刪除記錄 scriptlets 的 cannot apply rule 資訊 #313

在將規則轉換為 uBO 規則時，AdGuard 將逗號考慮在內 #343

改進了 prevent-xhr scriptlet #347

修正了 log-addEventListener 操作中的錯誤 #335

如果請求/網域被 DNS 過濾阻止，prevent-fetch 和 prevent-xhr scriptlet 無法提供幫助 #334

為 set-cookie 新增了 Accept 和 Reject 值 #336

為 set-cookie 設定了不區分大小寫的值 #342

修改了 google-ima3 以避免與 DAI SDK 沖突 #331

修改了儲存項目 scriptlet，增加了按鍵刪除項目的功能 #338

為 prevent-xhr 和 trusted-replace-xhr-response 模擬 getResponseHeader() 和 getAllResponseHeaders() 方法 #295

在調用 m3u-prune 和 xml-prune scriptlet 中的 send() 方法之前使用 addEventListener 時出現的收縮問題 #315

為 prevent-element-src-loading scriptlet 新增了防止內聯 onerror 和匹配 link 標記的功能 #276

trusted-set-cookie-reload，如果使用 $now$ 值，網站不會重新加載 #291

Cookie 設定 scriptlet，名稱和值編碼問題 #311

scriptlet 和重新導向中的 Response 實例屬性問題 #297

trusted-set-cookie 和 trusted-set-cookie-reload scriptlet 的值編碼問題 #320

修復 googletagservices-gpt — updateTargetingFromMap() #293

Scriptlet 應正確處理轉義引號 #286

應用程式顯示支援 scriptlet 或重新導向 #273

版本

將 CoreLibs 更新為 v1.12.75 #1294

將 DnsLibs 更新為 v2.2.27 #1299

CoreLibs

功能

新增了 HTTP/3（IETF QUIC）的支援（"h3" 協定） #487

遷移到新的 XPC 進程間通信系統 #1675

新增了 $to 修飾 #1714

新增了 $referrerpolicy 修飾 #135

修復

不支援 uBO 媒體查詢 #1707

如果 AdGuard 已在運行，WARP 會收到「無法連線」的錯誤 #1234

瀏覽 ipTIME 家庭路由器時出現幾秒鐘的延遲 #1756

如果啟用了 VPN 擴充功能，帶有 ECH 設定的 AdGuard 桌面版會阻止對域名之存取 #1751

AdGuard 會減慢網頁載入速度 #1522

例外規則相互幹擾 #1749

「隱藏您的搜尋查詢」選項運行不正確 #1766

在 mypikpak.com 無法使用修飾規則 #1767

啟用 network.https.ech.enabled 設定後，不支援 ECH 的網站將啟用 ECH GREASE #1781

處理腳本 text decryption key not found 時出錯 #1750

有時備援 DNS 助理返回 127.0.0.1，而不是供應商的伺服器 #1687

TCP/IP：新增了新的拒絕模式，因為行政禁止 ICMP #1774

TcpIpStack 中的 UDP 超時太短 #1796

使用者腳本 SaveFrom helper 從 ok.ru 網站下載影視時出錯 #1776

DnsLibs

功能

將 "lb._dns-sd._udp.*.in-addr.arpa" 新增到預設例外清單中 #194

修復

DoH 經常試圖使用過時的連線方式 #200

sdns:// 憑證固定不正確 #205

不要將 127.0.0.1 指向往外的代理 #195

UserscriptsWrapper

將 UserscriptsWrapper 更新為 v1.2.20

修復

imdb.com 的使用者腳本不起作用 #1729

在這次更新中，我們改進了「進階設定」的介面，把設定按字母順序排序，它們的名稱可以複製，列寬可以調整。現在還有一個轉到知識庫文章的連結。此外，我們修復了一些錯誤並更新了 Dnslibs。

更新記錄

功能

改進了「進階設定」#1222

新增了越南語的支援 #1224

修復

瀏覽器助理圖示在v2.10.1中隨機變成灰色 #1247

在 Safari 瀏覽器中，無法選擇要封鎖的 baidu.com 項目 #1246

使用往外的代理時無法匯出設定 #1249

捷克語「關於」部分有錯別字 #1225

版本

將 DnsLibs 更新為 v2.2.5 #1243

在這個修補程式中，我們修復了一個錯誤，該錯誤導致一些在主使用者腳本名稱中使用 unicode 的使用者腳本無法起作用。我們還改進了實驗性 Encrypted ClientHello（ECH）的功能，以確保它可以在 Kext 和自動代理過濾模式下工作。最後，像往常一樣，我們更新了 CoreLibs 和 DNSLibs。

更新記錄

修復

在 Kext 和 PAC 過濾模式下無法使用 ECH 功能 #1226

在 yandex.ru/images 無法使用 path 修飾符 #1738

自訂的使用者腳本在更新到v2.10後無法工作 #1229

過濾器的改進

$permissions 現在使用 Structured Field Values 語法而不是 CSP 語法 #1748

版本

將 CoreLibs 更新為 v1.11.98 #1237

將 DnsLibs 更新為 v2.1.38 #1236

適用於 Mac 的 AdGuard v2.10 版本帶來了許多新功能和各種改進。

預設啟用 DNS 過濾

「DNS 保護」預設啟用。現在所有的，而不僅是付費版的使用者，都可用 DNS 保護。如有使用者不使用 DNS 伺服器，軟體將自動選擇具有 AdGuard DNS 過濾的系統 DNS 伺服器。本改進非常重要，因為有它我們才可以引入另一個功能，即 Encrypted ClientHello (ECH) 的支援。

實驗性 Encrypted ClientHello 的支援

什麼是 Encrypted ClientHello？

目前，幾乎每一個 HTTPS 連線是加密的，沒有人可以查看其資訊。然而，連線的第一個數據包，即 ClientHello，包含使用者所連線的伺服器名稱。假設使用者想開啟 www.google.com，ISP 無法檢測使用者傳送和接收的資訊，但 ISP 知道使用者在與什麼網站進行通信。Encrypted ClientHello (ECH) 就解決該問題，對最後一點未加密的資訊進行加密，完全加密 HTTPS 連線。這意味著，第三方，比如網際網路服務供應商，無法檢測連線的資訊或使用者所訪問的網站。

AdGuard 並不是唯一支持 ECH 的軟體。 Chrome 和 Firefox 瀏覽器也在試圖實施對 ECH 的支援。但是，AdGuard 有一個顯著的優勢。

假設 Chrome 已經增加了對 ECH 的支援，這意味著，本功能只能在 Chrome 內起作用，不能擴展到其他應用程式和瀏覽器。相比之下，AdGuard 的 ECH 支援在 AdGuard 過濾的所有應用程式和瀏覽器中自動運作。因此，使用者不必等待作業系統或應用程式套用這一功能，因為有了 AdGuard，使用者就可以使用 ECH 的支援。

如何啟用 ECH 支援

要啟用 ECH 支援，請遵循以下步驟：

確保「DNS 保護」處於啟用狀態。ECH 依賴於通過 DNS 獲取的數據，因此為了讓 AdGuard 接收到這些數據，並為使用者在全系統範圍內啟用 ECH，需要進行 DNS 過濾。

請查看「封鎖 ECH」處於禁用狀態。本功能會幹擾 ECH 支援的正常運行。

前往「高級設置」並啟動 network.https.ech.enabled。

為了確保 ECH 工作正常，請使用以下方法：

前往 https://crypto.cloudflare.com/cdn-cgi/trace/ ，應該被顯示 sni=encrypted.

前往 https://defo.ie/ech-check.php，應該被顯示 SSL_ECH_STATUS: success.

限制和問題

ECH 是一項新技術，所以使用者在使用它時可能會遇到一些問題。

ECH 支援可能會減慢網頁加載速度。不過，我們正在努力解決這個問題！

請注意：ECH 支援必須在雙方實現。只有 AdGuard 支援本功能是不夠的，伺服器也必須支援它。ECH 是一項新技術，因此，目前支援它的伺服器數量還是比較少。然而，支援 ECH 的伺服器數量預計將會增長。

新進階設定

在進階設定使用者可以找到很多新功能，它們可以分為四個類型：

反 DPI 影響的選項允許對過濾請求進行低級別的修改，以保護使用者流量不受深度封包檢測（DPI）的影響

stealth.antidpi.clienthello.split.fragment.size

stealth.antidpi.http.space.juggling

stealth.antidpi.http.split.fragment.size

Keepalive 選項讓使用者配置與 Keepalive 連線有關的設定

network.tcp.keepalive.enabled

network.tcp.keepalive.interval.seconds

network.tcp.keepalive.timeout.seconds

DNS 相關選項幫助使用者微調 DNS 設定 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

憑證安全選項允許使用者按各種標準檢查網站和網路服務的憑證

network.https.enforce.certificate.transparency

我們升級了 CoreLibs、DnsLibs、Scriptlets 和 ExtendedCSS。此外，增加了烏克蘭語過濾器。

更新記錄

功能

「DNS 過濾」和「系統 DNS」預設為所有使用者被啟用#1217

新增了 Tor 瀏覽器的支援 #1045

新增了 Arc 瀏覽器的支援 #1188

通過 Safari 報告錯誤時，預設開啟一個新的分頁，而不是一個窗口 #1100

修復

當匯出項目名稱包含文檔系統的無效字符時，匯出失敗 #1198

如果應用程式在禁用「過濾器更新檢查間隔」的情況下啟動，網路服務無法連線 #1190

主畫面上與授權畫面上的授權期剩余天數不一致 #1177

在 MacOS 13 上讀取系統憑證儲存時，過濾服務崩潰 #1151

版本

CoreLibs

將 CoreLibs 更新為 v1.11.79 #1221

Encrypted ClientHello 的支援 #1565

新增了 HTTPS 例外的精確匹配語法 #1691

對普通 HTTP 實施「保護免於深層封包檢查（DPI）」 #1629

改進了因「無網路連線」而啟動網路擴充功能時的故障檢測 #1679

「保護免於深層封包檢查（DPI）」允許配置 HTTPS #1649

新增了簽名證書時間戳 (SCT) 的支持 #1529

暫停 AdGuard 時，Netbiosd 進程開始使用大量的 CPU #937

修復了丟失的 TCP/HTTP 連線 #1658

Brook 無法封鎖廣告 #1641

如果安裝了 NEAppProxyFlow.networkInterface，則使用 NEAppProxyFlow.networkInterface，而不是 RouteResolver #1677

修復了使用者腳本的 @match 字段的不正確工作 #1650

HTTPS 過濾打破 trading.finam.ru #1724

elearning.ual.pt 在啟用「保護免於深層封包檢查（DPI）」的情況下無法開啟 #4451

在結尾有點的網站上無法進行過濾 #1741

path 修飾符在 yandex.ru/images/ 不起作用#1738

DnsLibs

將 DnsLibs 更新為 v2.1.27 #1211

在應變域名新增了 tplinkdeco.net #175

在應變域名新增了 tplinkextender.net #183

在安卓的 IPv6-only 網路崩潰 #182

DNS 上遊超時導致許多請求待定 #40

Scriptlets

將 Scriptlets 更新為 v1.9.1

新增了新 m3u-prune 小腳本 #277

在 set-attr 小腳本中增加了更多可用的值 #283

改善了 'adjust-setTimeout和adjust-setInterval` 小腳本 #262

改善了 json-prune 小腳本 #282

修復了對 noopcss 重新導向的相容性 #299

修復了 google-ima 重新導向的相容問題 #272

修復了 prevent-addEventListener 和使用者腳本之間的相容問題 #271

修復了與 prevent-element-src-loading 有關的問題#270

修復了與 xml-prune有關的錯誤 #289

ExtendedCss

* 將 ExtendedCss 更新為 v2.0.51

IAffectedElement 的 style' 中的content' 屬性現在是可選的 #163

過濾器改進

新增裡 $permissions 修飾符 #419

新增了 $domain 修飾符的 regexp 支援 #1550

新增了 $url 修飾符 #1551

改進了 $redirect 語法與 uBO 的相容性 #1605

改進了 $jsonprune #1710

$jsonprune 修飾符應該成功處理 jsonp #1717

在應用轉換後的 uBO-syntax HTML 規則 ##^script:has-text() 時，將原始規則傳送到過濾記錄#1709

解決了將 HTML 過濾轉換為 uBO 的問題 #1708

$generichide + $generichide,badfilter導致保護不能被啟用/禁用 #1681

有時 $important 修飾符無法運作 #1695

$removeparam 例外無法運作 #1704

正確的規則被標記為無效 #1625

如果規則中包含~domain，元件隱藏例外就不起作用 #1673

從這個版本開始，對於剛剛安裝該應用程式的使用者，將預設啟用 DNS 保護。作為預設，AdGuard 使用使用者 ISP 提供的 DNS 伺服器，但您可以從清單中選擇另一個 DNS 伺服器，或是新增您自己的。要做到這一點，前往設定 → DNS，使用者還可以設定 DNS 過濾或關閉 DNS 保護。此外，我們還更新了波蘭語翻譯，修復了一些小錯誤，並升級了我們的核心過濾引擎，及 CoreLibs 和 DNSLibs。

更新記錄

更新

將 CoreLibs 更新為 v1.10.182 #1175

將 DnsLibs 更新為 v2.0.75 #1179

新增

PIX-LINK 路由器/中繼器域轉為後備域名 #170

Safari 瀏覽器助理中缺少波蘭語翻譯 #1174

這次更新我們修了一些惱人的錯誤。除此之外，我們更新了 CoreLibs、DnsLibs，以及 DNSCrypt 的 DNS 戳記。

更新記錄

[優化] 將 CoreLibs 更新為 v1.10.135 #1161

[優化] 將 DnsLibs 更新為 v2.0.56 #1162

[修復] macOS 13 公測版上安裝時出錯#1116

[修復] 有一些 regexp 規則無法運作 #1688

我們現在為大家隆重介紹 Mac 版 AdGuard v2.9.0！這次版本包含的更新都是經過了各種關卡測試，層層選拔的通關者。

在正題開始前，我們要強調：當前 AdGuard Mac 版不支持 macOS 10.12（Sierra）。AdGuard v2.9.0 支持的最低作業系統是，macOS 10.13（High Sierra）。下次更新後，支持的最低作業系統就會變成 MacOS 10.15（Catalina）了。

[優化]實現了通過過濾記錄新增規則的功能 #925

我們實現了 AdGuard Mac 版使用者一直以來都很期待的功能，即通過「過濾記錄」一鍵新增規則的功能。使用者只要開啟過濾記錄，選擇查詢排行，雙擊它，並點擊「封鎖」或「取消封鎖」。使用者規則新增就完成了！

[優化] 代理設定移至網路分頁 #734

我們把代理設定從普通使用者很少查看的進階設定遷移至應用程式設定中的「網路」分頁。現在，使用者很簡單就可以設定 AdGuard 往外代理伺服器。此外，使用者也可以在我們的部落格中找到如何在裝置上配置自己的代理並且與 AdGuard 一起運行的說明。

[優化] 進階設定中新增了一個新的日誌記錄部分 logging_item_zh-tw

現在，使用者能在同一個裝置裡選擇記錄級別，匯出記錄和系統資訊，並且重新設定記錄。我們還想要提醒使用者，只有在我們的支援團隊要求使用者切換到偵錯記錄後，才能這樣做，否則就使用預設記錄。

主要 CoreLibs 和 DnsLibs 更新

這次更新包含主要 CoreLibs 和 DnsLibs 更新。現在，在 CoreLibs v1.10.113 可以過濾 DNS-over-HTTPS，並且使用 $jsonprune 修飾符。包含 $stealth 修飾符的規則可以禁用一些隱匿模式的選項，包括「保護免於深層封包檢查（DPI）」。我們還更新了小腳本庫。

大幅更新的 DNS 過濾庫 DnsLibs v2.0.30 版本現在消耗的資源更少，而且運行的速度更快。DNS-over-QUIC 協定的實現現在可以支持 RFC 9250 標準，並且從 DoQ 协定的支持中移除實驗性狀態。

當然，除了解決以上一些比較大的問題外，我們還解決了不少小錯誤，讓 AdGuard 運行更流暢。我們希望使用者都會喜歡 Mac 版 AdGuard 2.9.0 的使用體驗！

更新記錄

[優化] 在 DNS 分頁中為「一般」DNS 伺服器描述新增了「未加密」圖示 #1034

[優化] 如果禁用 AdGuard 防護，則不再顯示應用程式退出確認 #1079

[優化] 刪除 AdGuard 穩定（發佈）版本編號中的發佈一詞。#1099

[修復] 將新網站新增到允許清單時，之前新增的網站會被刪除#1056

[修復] 關於關閉 AdGuard 的確認資訊沒有出現在其他應用程式的頂部 #1058

[修復] 當網路關閉時，通過網路擴充功能進行過濾初始化時出現錯誤 #1124

[修復] 啟用 AdGuard 時出現記憶體流失 #1092

[修復] AdGuard 在睡眠模式下不過濾廣告請求 #994

對過濾器的建立者很重要

[優化] 過濾器元數據解析被移至 CoreLibs

[優化] 實現了通過過濾記錄新增規則的功能 #925

[優化] 增加了對使用 $jsonprune 規則編輯 JSON 回應的支持 #1447

[優化] 增加了一個新的修改器，用於處理 HLS（m3u8）文檔 #1434

[優化] 擴大了 $stealth 修改器的功能範圍 #1224

[優化] 增加了對非基本規則的空$path修改器的支持 #1591

[優化] $removeparam 可以應用於 POST 請求#1573

[修復] 從第三方隱藏使用者的 Referrer 的隱匿模式選項幹擾了 $third-party 的修飾語 #1640

[修復] 包含 :where() 偽類的規則被拒絕 #1609

[修復] 修復過濾器中的預處理程序指令

將 CoreLibs 更新為 v1.10.113

[優化] 增加了對使用 $jsonprune 規則編輯 JSON 回應的支持 #1447

[優化] 應用了 DoH 請求的過濾
#1563

[優化] 擴大了 $stealth 修改器的功能範圍 #1224

[優化] 封鎖器不計入過濾器清單中 #1667

[優化] 過濾器元數據解析被移至 CoreLibs

[優化] 增加了一個新的修改器，用於處理 HLS（m3u8）文檔 #1434

[優化] 增加了對非基本規則的空 $path 修改器的支持 #1591

[優化] $removeparam 可以用於 POST 請求 #1573

[修復] 包含 $third-party 修飾語的規則封鎖來自網站子域的資源。 #1637

[修復] 從第三方隱藏使用者的 Referrer 的隱匿模式選項幹擾了 $third-party 的修飾語 #1640

[修復] 在 macOS 上處理旁路連接時的記憶體流失問題 #1643

[修復] AdGuard Mac 版阻止對 wwww.mindray.com 的訪問 #1648

[修復] 包含 $all 修飾語的規則不阻止訪問的網站 #1590

[修復] AdGuard Mac 版阻止 Microsoft Edge Collections #1653

[修復] 包含 :where() 偽類的規則被拒絕 #1609

將 DNSLibs 更新為 v2.0.30

[修復] 搜尋 DNS64 出錯 #1142

[其他] 在進階設定中增加了新的選項 阻止 "Encrypted ClientHello" 參數 #161

[其他] 在構建項目時，出現了關於連線到 dylib 的警告，這對於應用擴充功能來說是不安全的 #136

這次技術更新，我們提高了應用程式的穩定性並修復了一些程式錯誤。

我们不久之前刚更新了应用程序，但追求完美的我们又做了一些小修小补。我们修复了一些与 DNS 有关的过滤，以及与用户界面有关的错误。像往常一样，我们也更新了 CoreLibs 并进行了其他改进以让应用程序运行更顺滑、完美。

更新日志

[优化] 将 CoreLibs 更新为 1.9.62

[修复] 有时当用户导入 DNS 规则/网域时，AdGuard 会崩溃

[修复] 由于数据库故障导致的应用崩溃

[修复] 当用户切换标签时，DNS 设置界面错误

[修复] 黑名单和白名单的搜索栏消失

[修复] AdGuard 无法检测 DNS 配置文件

[修复] 在「已过滤的应用程序」部分的滚动条行为

我们上次发布 AdGuard Mac 版更新的时候还是圣诞节之前。现在是西方的复活节，终于迎来了2022年的首次更新。这次更新包括三个重要更新。第一个是，广大 Mac 用户催促已久的设置导出/导入功能终于来了，本功能已经在每一款 AdGuard 产品中都有了，Mac 版是最后一个吃螃蟹的人。现在好日子来了，Mac 版的用户终于也可以批量导出和导入他们的设置了，辛苦大家久等了！

第二个功能是，现在用户安装 AdGuard 应用程式时会看到更多对话框。安装时 AdGuard 需要不少访问权限而且也确实会对用户的系统配置执行很多改变。更重要的是，AdGuard 将建立并安装一个证书用于执行 HTTPS 过滤。出于尊重用户隐私安全和对安全隐患的理解，我们决定要向用户解释 AdGuard 要求的所有权限。这一点非常重要。毕竟，大家安装 AdGuard 原因不就是看中AdGuard 广告拦截力强而且尊重用户隐私吗？因此，借在关于此证书的新对话屏幕上的机会，我们再次坚定声明我们的宗旨：除了过滤广告之外我们不会将在用户的系统上获得的权限用于任何其他目的，永远不会。

最重要的功能压轴登场，我们添加了能够改善用户隐私保护的选项，即反 DPI。在部分情况下，本功能可以防止用户 ISP 的数据包的深度检测技术检测到用户访问的网站。可以说反 DPI 功能是我们对网络中立性的投入。

我们还修复了程序错误（解决了当应用程序属于开启状态时浏览器扩展图标不知不觉改成灰色的问题）。像往常一样，我们改善了 CoreLibs 和 DNSLibs 以让应用程序使用体验更流畅。希望大家满意！

更新日志

[优化] 增加设置导出#514

[优化]增加一个对话框，说明 AdGuard 需要运行一个根基工具以配置系统#977

[优化]启用和禁用保护的快捷方式#879

[修复] 浏览器助手图标随机变灰 #1025

[修复] 如果列表中不包括最后更新，则不显示最后更新 #1022

[修复] 向 AdguardFilters 报告问题时缺少用户脚本#1033

[修复] 在 Safari 中打开 AdGuard 助手时，AdGuard 有时会崩溃#1016

CoreLibs 更新为 v1.9.60

[优化] 在隐形模式添加了反 DPI 选项#1615

[修复] Kinopoisk.ru 的授权问题#1502

[修复] 一些正确的规则无法运行#1531

[其他] 支持快速速度/Adguard 锁定在 300mbp/s #1561

[其他] Facebook 图片上传不工作 #1588

[其他] DnsLibs 更新为 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 版本

更新記錄

改進

修復

CoreLibs（過濾引擎）

改進

修復

UserscriptsWrapper

修復

ContentScript

修復

DnsLibs（DNS 過濾引擎）

更新記錄

修復

CoreLibs (Filtering engine)

DnsLibs (DNS filtering engine)

更新記錄

修復

將 CoreLibs （過濾引擎）更新為 v1.14.51

改進

修復

其他

將 DnsLibs（DNS 過濾引擎）更新為 v2.5.18

改進

其他

UserscriptsWrapper 更新為 v1.2.23

將 Scriptlets（過濾規則的 JavaScript 改進）更新為 v1.10.25

改進

修復

提高 HTTPS 過濾的透明度

HTML 過濾規則選擇器的支援

新 DnsLibs 和基本 HTTP 驗證

更新記錄

改進

修復

CoreLibs（過濾引起）

改進

修復

DnsLibs（DNS 過濾引擎）​

修復

過濾器改進

Scriptlets（過濾規則的 JavaScript 改善）

改進

修復

UserscriptsWrapper

更新記錄

修復

CoreLibs（過濾引擎）

更新記錄

修復

CoreLibs

DnsLibs

更新記錄

功能

修復

過濾器的改進

功能

修復

Scriptlets

將 Scriptlets 更新為 v1.9.62

功能

修復

版本

CoreLibs

功能

修復

DnsLibs

功能

修復

UserscriptsWrapper

將 UserscriptsWrapper 更新為 v1.2.20

修復

更新記錄

功能

修復

版本

更新記錄

修復

過濾器的改進

版本

DnsLibs（DNS 過濾引擎）