Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
General Apps
AdGuard
AdGuard Browser Extension - Stable Updates Thread
Message
<blockquote data-quote="JasonUK" data-source="post: 966197" data-attributes="member: 86995"><p>It's interesting to see how v4 beta is changing some of the user rules that I had set up in v3 when copied across ~ examples of each change below together with comment what original rule was aiming to achieve! The TLD's blocked are taken from Spamhaus' list of most abused TLDs at <a href="https://www.spamhaus.org/statistics/tlds/" target="_blank">The Spamhaus Project - The Top 10 Most Abused TLDs</a></p><p></p><p>! --- Block downloading executable content from insecure HTTP websites</p><p>|http://*.exe^$empty</p><p></p><p>Becomes:</p><p>|http://*.exe^$redirect=nooptext</p><p></p><p>! --- Block all on much abused country code TLD's. The TLD is between ||* and ^$, e.g. ||*.AM^$</p><p>||*.cn^$all</p><p></p><p>Becomes:</p><p>||*.cn^$document,popup</p><p>||*.cn^$csp=script-src 'self' 'unsafe-eval' http: https: data: blob: mediastream: filesystem:</p><p>||*.cn^$csp=font-src 'self' 'unsafe-eval' http: https: data: blob: mediastream: filesystem:</p><p>||*.cn^</p><p></p><p></p><p>I won't pretend to understand structure of new rules but they block the TLDs effectively enough (same blocking screen as AdGuard for Windows). Blocking the TLDs are probably unnecessary to be honest as chances of visiting most of them are slim to nil so I might delete those anyway.</p></blockquote><p></p>
[QUOTE="JasonUK, post: 966197, member: 86995"] It's interesting to see how v4 beta is changing some of the user rules that I had set up in v3 when copied across ~ examples of each change below together with comment what original rule was aiming to achieve! The TLD's blocked are taken from Spamhaus' list of most abused TLDs at [URL='https://www.spamhaus.org/statistics/tlds/']The Spamhaus Project - The Top 10 Most Abused TLDs[/URL] ! --- Block downloading executable content from insecure HTTP websites |http://*.exe^$empty Becomes: |http://*.exe^$redirect=nooptext ! --- Block all on much abused country code TLD's. The TLD is between ||* and ^$, e.g. ||*.AM^$ ||*.cn^$all Becomes: ||*.cn^$document,popup ||*.cn^$csp=script-src 'self' 'unsafe-eval' http: https: data: blob: mediastream: filesystem: ||*.cn^$csp=font-src 'self' 'unsafe-eval' http: https: data: blob: mediastream: filesystem: ||*.cn^ I won't pretend to understand structure of new rules but they block the TLDs effectively enough (same blocking screen as AdGuard for Windows). Blocking the TLDs are probably unnecessary to be honest as chances of visiting most of them are slim to nil so I might delete those anyway. [/QUOTE]
Insert quotes…
Verification
Post reply
Top