To kick things off for AdGuard v2.3 for Mac we release this small-ish beta. It’s mostly focused on fixing network- and UI-related bugs, there’s also a new Stealth Mode parameter to block Java.
- [Added] “Block Java” option to Stealth Mode #476
- [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] AdGuard reinstalls SSL certificates upon each system reboot #628
- [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.141 #649
We’re making final touches in our preparation for v2.2 release: a few minor changes and the ever present CoreLibs update. This time, there’s a couple of really important CL changes:
[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.
$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 to block ads more efficiently.
We should mention that both
$rewrite modifiers are still kind of working in test mode, but they are fully operational and you should feel free to use them.
- [Changed] Edge icons have been updated #641
- [Changed] Opera Beta and Opera Dev added to the list of apps filtered by default #621
- [Fixed] AdGuard icon is invisible #527
- [Fixed] Remotix compatibility issues #592
- [Fixed] Custom userscripts can’t resolve URLs with non-English symbols #640
- [Improved] CoreLibs has been updated to v1.5.113 #636
- [Improved] AdGuard now can parse
Last modifiedparameter of custom filters #409
It’s time to embark on a quest for the next AdGuard for Mac big update! And our first step is to release this beta: it features added support for custom userscripts and new way to activate AG, but also several bugfixes and other lesser changes.
[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] “Trusted” flag for custom filters #521
- [Fixed] “Untrusted CA certificate” issue #596
- [Fixed] Extra “AdGuard Extra” userscripts #607
- [Fixed] Editing user filter doesn’t work when search box is not empty #569
- [Improved] Installer icon updated to match the app’s icons #584
- [Improved] Voiceover accessibility #634
- [Improved] CoreLibs has been updated to v1.5.99 #635
- [Improved] Localizations have been updated
We’re approaching the next release, and the betas are becoming less saturated with changes but more focused. In this one, the main attention is drawn to CoreLibs. After some tweaks made to the filtering engine, now connections will not be reset as often: only in rare cases when filter updates or changes in configuration require it. Few other improvements:
In the first beta version after v2.0 release we mostly concentrate our efforts on fixing various compatibility issues and other bugs. We also added automatic filters detection.
[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
- [Fixed] No internet connection with custom DNS in DNSCrypt #528
adguard-tcpkillprocess constantly crashes on macOS Catalina #530
- [Fixed] “Reset Settings” option hangs the app #543
- [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] Localizations have 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
A small beta to fix some of the more unpleasant bugs and improve filtering quality.
- [Fixed] Status of the "Trusted" checkbox isn't saved for custom filters #519
- [Fixed] Pages don't load when two system user accounts are in use #509
- [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
- [Improved] CoreLibs engine has been updated #522
CoreLibs is the centerpiece of the upcoming AdGuard 2.0 for Mac update, and we've just discovered some minor problems with it. Nonetheless, we consider them important enough to release one more beta to fix these problems before unleashing the new stable version into the world. We've also made a few localization updates.
Welcome the first AdGuard 2.0 for Mac release candidate! The changes are minimal compared to the recent beta, but there’s one that’s worth your attention: the introduction of AdGuard Extra userscript. By the way, we plan to transition this version into a stable one if everything goes well.
[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.
[Fixed] Description for “Strip tracking parameters” option #398
[Fixed] The list of filtered apps gets reset after an update #473
[Fixed] Vivaldi browser is not filtered #475
[Fixed] Microsoft Edge browser is not filtered #487
[Fixed] AdGuard doesn’t start automatically on the system startup #480
When it comes to AdGuard for Mac, we prefer a steady, even methodical approach. Eliminate all bugs, make sure nothing is left unnoticed. This is one of those betas where we clean everything up: fix bugs, improve some of the features and so on. We’ll let it run for a while, monitor it for anything that resembles a missed bug, and if is all is good, we’ll stick a “2.0 stable” label 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.
NOTE: if you currently have AdGuard installed to any folder except for
- [Added] An indicator for modified cookies in the Filtering Log #386
- [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] 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] Whitelist shows comments from User Filter after update #452
- [Fixed] Compatibility problems
- [Added] Stealth Mode parameters to the web reporter link #388
- [Fixed] Stealth Mode actions aren't showed in the Filtering Log #355
- [Added] A description in the Filtering Log for some types of Stealth Mode events #421
- [Added] Trusted filter notification #445
- [Added] New AdGuard for Mac icon #450
- [Fixed] Blocked 'WebRTC, location API, push API' events aren't shown in modified requests in Filtering log #449
- [Fixed] Two notifications appear after using the manual ad blocking tool #419
- [Changed] Users with an active subscription will not be notified anymore that their license key is soon to expire #329
- [Changed] Localizations has been updated
adguard-tcpkilldoes not work with the new Chrome version #427
- [Fixed] Changes to the filtered apps and extensions are not applied until the protection is restarted manually #354
- [Fixed] Forwarder applied properly to all links in the app #389
- [Fixed] The app hanged on exit #462
- [Fixed] Filtering Log issues #430
- [Improved] Enhanced app accessibility #406
AdGuard for Mac traditionally doesn’t receive frequent updates, but when it does, it is usually something big. This beta is not an exception, we present to you not one, not two, but three big changes, each one of them would normally be enough to justify a beta update on its own. These changes are CoreLibs integration, new UI and the introduction of Stealth Mode. Let’s jump inside and look at them more closely.
[Added] CoreLibs integration #232
This is the first AdGuard for Mac beta 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] “Application” column to the Filtering Log #341
- [Added] “Export logs and system info...” option #395
- [Changed] Users with an active subscription will not be notified anymore that their license key is soon to expire #329
- [Changed] Exception rules created via Assistant now have $document,~extension modifiers #333
- [Fixed] High CPU usage due to a sync XHR request made by the Assistant #315
- [Fixed] Statistics is not counted properly #334
- [Fixed] Kext status check does not work properly on macOS 10.14 #337
- [Fixed] Website report is now sent properly via the Assistant #361
- [Improved] Refactoring “Launch at Login” #415
- [Improved] New onboarding screens #385, #407
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 v1.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
- [Fixed] No default filters on clean install #360
- [Fixed] Welcoming UI and app menu are broken in dark mode on Mojave #359
This is a necessary beta version, tonight we will push this beta into release channel.
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
This is a necessary beta version, tonight we will push this beta into release channel.
This beta brings a hotfix for an issue when a combination of bad connectivity and specific environment leads to blocked network access. We have also made some changes to support the upcoming Japanese translation.
- [Fixed] [Fixed] TCP FastOpen incompatibility #309
- [Changed] [Fixed] Compatibility with Boxcryptor #310
- [Fixed] Browser connections are blocked in certain circumstances #306
- [Fixed] High CPU usage due to a sync XHR request made by Assistant #315
This update brings just one small fix and becomes our new release candidate.
[Changed] Adguard downgrades TLS version in case of connection error #300
It’s been a while since the last AdGuard for Mac release, so we owed one to our Mac users. This beta is small but impactful — or at least we hope so. Some important bugfixes and key improvements have been done.
[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 beta.
[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.).
- [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
- [Improved] AdGuard UI files have been altered to use modern approach in localization #273
Ho ho ho! Merry Christmas and happy New Year to all of you! And, of course happy Hanuka, or any other holidays that you may be celebrating these days! A small present by our AdGuard for Mac developers for all of our Mac beta-testers. This beta version holds one major change/improvement, and a couple of minor ones. Details below, as usual.
[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.
Here’s a first AdGuard for Mac beta in a while. Why are they so rare? Because AdGuard for Mac is nigh perfect, of course! Jokes aside, we did some serious work here, further upgrading the ad blocking and improving the UI.
[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.
- [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
[Added] "undo/redo" buttons to the user filter editor #227
Self-explanatory. Working with filter editor has become so 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
- [Fixed] "Shadowsocks-R" and AdGuard compatibility problem #240
There was an updater bug in the last beta and, unfortunately, an in-app update to a newer version will cause an error. If you are using the previous beta 1.5.0 (395), please download the new 1.5.0 (400) version and replace the old one. Earlier versions are not affected by this bug.
The preparation for the release is going full steam ahead, and this update is actually a release candidate. Several bugs of the Filters section interface (#236, #237) have been fixed, we’ve made changes to the spelling of our brand name (#231) and have addressed some of the minor problems.
- [Fixed] AdGuard doesn't filter apps from the WebCatalog app #165
- [Fixed] Content rules are applied even when there is a `$document` exception #234
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 beta-version.
- [Fixed] Several network errors and compatibility issues.
We keep working on the next release and it is time to introduce a new beta version. Since in macOS High Sierra all system extensions need a special permission from a user, this new version brings a necessary change to Adguard for Mac - an additional startup tutorial (#217). There are also some important security (#224) and performance (#220) fixes along with a UI enhancement: Now it's possible to reset all settings in "Advanced" section of "Preferences" menu (#180). All changes below.
- [Fixed] Wrong cyphers order #224
- [Fixed] Adguard Crashes when receives new metadata from backend #220
The new AdGuard for Mac beta is a long-awaited one, and we tried to deliver. Basically, all the aspects of the program has been improved: many adblocking-related issues to improve the filtering quality, enhanced network security and reworked User filter. More details below.
- [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[ 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
- [Added] An option to exclude websites with EV certificates from filtering #170
- [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] There is an empty response from local.adguard.com in some cases when HTTPS is used #206
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.
- [Improved] Filter editor has been reworked #56
- [Fixed] The 'expiring trial' warning translation #169
- [Fixed] The number of remaining subscription days is not displayed in Adguard toolbar #191
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.
- [Improved] Adguard can now be launched from an external drive #210
- [Changed] The SSL exceptions list has been updated
- [Fixed] Yandex mail compatibility issue #160
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.
We are getting closer and closer to Adguard for Mac release. This means we don't want any, even insignificant bugs and errors left. This is why we are willing to release beta versions with a changelog this small. To be more precise, this is a release candidate - if everything is fine with it, it will become a new release.
In this small beta we make several changes, which mostly concern networking.
- [Changed] Updated default HTTPS exclusions list #124
- [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
- [Improved] Adguard styles are now protected from removal #149
It was a long while since the last Adguard for Mac update. We hope it was worth waiting, because new beta adds the support for Extended CSS - read below why it is so important. Besides that, an awful lot of other fixes and changes that will reflect positively on the performance.
- [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
- [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
- [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
- [Improved] Content injection algorithm #119
New beta features few changes and mostly concerns network issues.
Greetings! It is time to release new beta version of Adguard for Mac. 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. Optimizing basic filtering rules (#91) processing is very important since basic rules are the most resourse-consuming among all. #88 also deserves attention. Now we lower resourse consumption significantly during the 'idle time'. Overall, Adguard will become faster now, but not only that. Thanks to the better performance, Adguard will now consume significantly less battery resourse.
[Added] A notification that is shown if user unchecks the "Filter https protocol" box #65
Languages and Translations
[Added] Finnish language #63
- [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
- [Improved] Basic filtering rules processing speed was optimized #91
- [Changed] Connections are not kept alive for too long now if 'HTTP keep alive' timeout is specified #88
- [Changed] Webdav methods are supported now (specifically REPORT) #85
- [Fixed] After blocking a POST request, next request is read only when data was read to end #68
- [Added] Support for complex language codes #78
- [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
- [Added] $replace modifier for basic rules.
- [Changed] Suppress browser cache after filtering startup for a short period of time.
- [Changed] Improved compatibility with sites that use the Content-Security-Policy mechanism.
- [Fixed] Modifiers for the whitelist rules do not work while filtering the content.
- [Added] New localizations: Serbian (Latin), German, Italian, Spanish (Spain), Chinese Traditional, Armenian, Turkish, Korean, Indonesian, Hungarian.
- [Added] User warnings in case HTTP proxy mode fails to start.
- [Changed] SHA-1 certificate outdating is now taken into account.
- [Changed] User filter is now loaded last, after all other filters are loaded.
- [Changed] Now $popup rules modificator is also applied to server redirect responses.
- [Fixed] Error previously led to inability to change HTTP proxy port with HTTP proxy mode enabled.
- [Fixed] Lack of explanation text in the 'Enter email address' text field.
- [Fixed] Template modificator * in rules now takes into account line break symbols.
- [changed] Now clicking on Adguard icon in status bar brings opened Adguard windows to front and makes them active.
- [changed] Now status 500 is always returned for blocked requests.
- [changed] Assistant requests are now excluded from 'Filtering log'.
- [fixed] Problem when Adguard extension for Google Chrome couldn't see triggered $genericblock rules. Integration mode works correctly now.[fixed] Problem when Adguard caused browser to freeze.
- [fixed] Problem when basic rules were treated as rules with $popup modificator.
- [added] $generichide rule modifier.
- [added] $genericblock rule modifier.
- [changed] If a website requires client certificate at SSL connection, then Adguard will pass traffic without filtering it.
- [changed] Updated list of SSL exceptions.
- [changed] Port on which Adguard accepts connections.
- [changed] A method of domain check with Browsing Security filter. Improved privacy of requests.
- [fixed] Third-party requests filtering error.
- [fixed] Error in css-inject rules.
- [fixed] Safari inability to connect to some websites with IPv6 network configuration.
- [fixed] Now $elemhide rule modifier is applied only to HTML-pages.
- [fixed] Error in finding the elements path on a page for HTML filtering rules.
- [fixed] Improved $popup modifier.
- [fixed] Error in HTML filtering rules – empty elements were never removed.
- [fixed] Blocking of Google Chrome Rapportive extension for Gmail.
- Improved compatibility with new OS X 10.11
- Fixed some app crashes
- Fixed an issue with OCSP staple check when valid cert might be considered as invalid.
- Added first launch tutorial screen.
- Added OCSP Stapling support.
- Added support for browsers: Firefox Nightly, Chrome Canary.
- Improved root certificate installation method for Mozilla-based browsers.
- Now Adguard system components are stored in the folder shared for all users.
- Fixed error previously preventing rules with particular symbols from traffic filtering.
- Fixed error previously causing incorrect Adguard closing.
- Improved security for adding Adguard Assistant to web pages.
- Improved mechanism of generating a root certificate and a private key for SSL connections.
- Fixed Logjam exploit (Adguard no longer filters connections with weak keys).
- Restricted access to the functions of userscripts API.
- Now when switching to sleep mode on Mac, Adguard closes the current network connections.
- Changed installation process, fixed problem when Adguard won’t work after restoring Mac from Time Machine.
- Fixed an error which led to the crash of previous beta version.
- Significantly increased list of browsers filtered by default.
- Added localizations: Chinese (simplified), Korean, Polish, Portuguese (Brazil), Slovak, Korean. v
- Added function to send a report upon unexpected Adguard shutdown.
- Improved filtering rules correctness check.
- Improved SSL-connections processing mechanism.
- Altered SSL-connections cipher suite to a modern one.
- Now Adguard automatically suggests to install root certificate into Firefox if there is none, to allow HTTPS pages filtering.
- Improved Adguard API extensions security.
- Fixed issue when Adguard won't respind to users actions while watching a YouTube video.
- Fixed error lead to Adguards crash while visiting a website with incorrect HTML.
- Fixed an error that used to cause incorrect filtering in v.1.0.58
- Truly improved performance.
- Fixed an error that used to decrease filtering speed in previous beta update, instead of increasing it.
- Added Ukrainian localization.
- Improved speed optimization.
- Improved security upon filtering encrypted traffic.
- Removed splashscreen upon starting Adguard.
- Now automatic check for updates is enabled by default
- 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
- Fixed several errors that could previously lead to app crash