- Jan 26, 2020
- 1,628
You mean if I don't use DNS function in the Adguard for Windows?Yes. If you don't use dns function you can turn it off.
You mean if I don't use DNS function in the Adguard for Windows?Yes. If you don't use dns function you can turn it off.
Yes.You mean if I don't use DNS function in the Adguard for Windows?
Ever since Adguard changed the person responsible for the Annoyances filter, it has been useless at best.I noticed that browsing slows down considerably when some features are activated or more lists are added from what's offered. Thinks speeded up when I reset settings to default. To minimize the cookie notification popups in some sites, I also had to activate Fanboy's Annoyances.
We once again reviewed GitHub repo and realized that we had been working for almost six months on version 7.7. And less than two months on version 7.8. Yes, there were fewer tasks in this version, but we did a good job on improving everything: Browsing Security, network drivers, CoreLibs and DNSLibs, other minor features, and – hopefully – your user experience.
[Enhancement] Browsing Security
Browsing Security is a module that blocks requests to malicious and phishing websites. You might have seen a nice looking banner caringly stating "AdGuard has blocked access to this page": that's what Browsing Security does. Now it's working a way better: requests for information about malicious domains are not sent to a server, but to a periodically updated database stored locally on your computer. This is faster and safer.
[Enhancement] WFP and TDI network drivers
We've also updated and enhanced our network drivers for Windows – WFP and TDI. Both have been helpful, among other things, to improve compatibility with other applications.
Other good stuff
And of course, there is no release without updating CoreLibs, our main filtering engine, and DNSLibs. Meet their new versions: more flexible, more powerful. As always: minor bugs have been fixed. As always: perfection has no limits.
Hope that your holidays will be safer with AdGuard.
Hi, isn't it better to also add easy privacy?Filters i use :
Adguards own filters
- adguard base filter
- adguard url tracking filter
- adguard tracking protection filter
- adguard social media filter
- adguard annoyances filter
Other built in filters i have enabled:
- no coin filterlist
- ablock for finland
Imported filters:
- 1hosts lite
Im using adguards tracking + url tracking + fanboy enchanted tracking list nowadaysHi, isn't it better to also add easy privacy?
Before a big release, it's a good idea to double-check everything and get rid of even the smallest problems. That's why today we're launching a release candidate of AdGuard v7.13 for Windows.
We’ve updated CoreLibs and DnsLibs, fixed a few bugs, including the compatibility issue with NordVPN, and improved the Browser Assistant.
Changelog
Fixes
- NordVPN interferes with the work of AdGuard if AdGuard’s DNS module is enabled #4673
- Upon exiting AdGuard, the Assistant indicates that AdGuard is not installed or misconfigured #4663
- Incorrect translation in the updater window #4640
- Disabling the Enable traffic filtering option does not stop filtering #4657
- The path modifier does not work on yandex.ru/images #1738
- The $jsonprune modifier can’t handle jsonp #1717
- Filtering does not work on websites with dot at the end #1741
- In some cases filtering doesn’t work on Google-related websites (e.g. youtube.com) #4480
Versions
As spring arrives, AdGuard for Windows unveils its latest release, complete with numerous new features and improvements.
Experimental Encrypted ClientHello support
Notably, the addition of experimental support for Encrypted ClientHello (ECH) is worth mentioning. This new technology fully encrypts HTTPS connections, concealing server names you are connecting to from ISPs and ensuring complete privacy.
So that you can benefit from it, we’ve added the Use Encrypted ClientHello feature to the Advanced settings section and enabled DNS protection by default for all users.
New Advanced settings
We’ve also added 16 more features to the Advanced settings section. A detailed description of each feature can be found in our Knowledge base.
All new advanced features can be divided into six groups:
Note that before v7.12 the AdGuard's service started in filtering mode by default (even if the Launch AdGuard at system start-up was disabled). If you were satisfied with the old behavior, enable this option.
- Anti DPI options allow to modify packets at a low level during filtering to prevent tracking via deep packet inspection
- Adjust size of fragmentation of initial TLS packet
- Add an extra space to the plain HTTP request
- Plain HTTP request fragment size
- Keepalive settings allow to configure settings to work with keepalive connections
- Enable TCP keepalive
- TCP keepalive interval
- TCP keepalive timeout
- Filtering exclusion settings allow to exclude both Wi-Fi networks and particular subnets (specified in the CIDR notation) from DNS filtering
- Exclude specified IP ranges from filtering
- IP ranges excluded from filtering
- Exclude specified Wi-Fi network names (SSID) from DNS filtering
- DNS-related options allow to fine-tune DNS settings
- Use fallback DNS upstreams
- Use HTTP/3 for DNS-over-HTTPS
- Query DNS upstreams in parallel
- Always respond to failed DNS queries
- Certificate security options allow to check certificates of websites and web services
- Check websites' certificate transparency
- Enable asynchronous OCSP SSL/TLS certificate revocation checks
- Enable filtering at system start-up. Now by default, AdGuard for Windows does not filter traffic after OS startup if the option Launch AdGuard at system start-up is disabled. If you want filtering to be performed even if AdGuard is not launched, you should enable this option.
What else? Aside from the regular CoreLibs and DnsLibs updates, we’ve updated WFP and TDI drivers and ExtendedCSS. We’ve also allowed to disable the Filter localhost advanced feature. But be aware that disabling this feature will prevent AdGuard Ad Blocker and AdGuard VPN from working simultaneously.
For Encrypted ClientHello technology to work, it must be supported on both client and server sides. Today, ECH support is implemented in a limited number of applications. Chrome and Firefox, for example, are in the process of adding it. Here we have no choice but to wait. But thanks to AdGuard, ECH support will automatically work in all apps and browsers on your device.
To check whether ECH is working, you can:
- Go to https://crypto.cloudflare.com/cdn-cgi/trace/ and see if it says sni=encrypted.
- Go to https://defo.ie/ech-check.php and check if it says SSL_ECH_STATUS: success.
As the Use Encrypted ClientHello feature is experimental, it may also lower your browsing speed a bit. But, we're currently working on solving this issue.