Reply to thread

Message

<blockquote data-quote="Windows_Security" data-source="post: 752040" data-attributes="member: 50782">Now Chrome blocks (nou user initiated iframe) redirects, the&nbsp; risk of third-party on Windows10 (with AppContainer) is further reduced. Now tweakers seem to loose another favourite optimization hobby (called what blocklist filters do you use). On my wife&#039;s Yoga 520 I use below settings for chrome and have AdGuard with optimized blocklists. No need for micro management third-party blockers any more IMO, when you only allow HTTPS from certain high level domains (Note: HTTPS is called secure, but that only applies on transmission protocol, not on the website itself, a HTTPS website can still be used to host malware). I only keep an eye on [USER=51905]@Evjl&#039;s Rain[/USER] tests on extensions (his tests show that with MBAM, WD or Comodo extensions all malware filters in ad/script blockers are just a waist of memory and CPU cycles).Update of flags I use (, plus high level domain blocks of cookies and javascript. When cookie or javascript is blocked the cookie or javascript icon appears in the address bar. Click on it and you can define exceptions. Ii enable com,net,org,inf and net by default plus websites with high level domain NL (netherlands as showed in javascript example on the right).The chrome semantic is<a href="HTTP://*" target="_blank">HTTP://*</a><a href="HTTPS://*" target="_blank">HTTPS://*</a>FILE:///*This can be combined with high level domain wildcards like[*.]com[*.]org[*.]gov[*.]eduetcExample of combination would be<a href="HTTPS://[*.]inf" target="_blank">HTTPS://[*.]inf</a>[ATTACH=full]193597[/ATTACH][ATTACH=full]193604[/ATTACH]</blockquote>

[QUOTE="Windows_Security, post: 752040, member: 50782"] Now Chrome blocks (nou user initiated iframe) redirects, the risk of third-party on Windows10 (with AppContainer) is further reduced. Now tweakers seem to loose another favourite optimization hobby (called what blocklist filters do you use). On my wife's Yoga 520 I use below settings for chrome and have AdGuard with optimized blocklists. No need for micro management third-party blockers any more IMO, when you only allow HTTPS from certain high level domains (Note: HTTPS is called secure, but that only applies on transmission protocol, not on the website itself, a HTTPS website can still be used to host malware). I only keep an eye on [USER=51905]@Evjl's Rain[/USER] tests on extensions (his tests show that with MBAM, WD or Comodo extensions all malware filters in ad/script blockers are just a waist of memory and CPU cycles). Update of flags I use (, plus high level domain blocks of cookies and javascript. When cookie or javascript is blocked the cookie or javascript icon appears in the address bar. Click on it and you can define exceptions. Ii enable com,net,org,inf and net by default plus websites with high level domain NL (netherlands as showed in javascript example on the right). The chrome semantic is [URL]HTTP://*[/URL] [URL]HTTPS://*[/URL] FILE:///* This can be combined with high level domain wildcards like [*.]com [*.]org [*.]gov [*.]edu etc Example of combination would be [URL]HTTPS://[*.]inf[/URL] [ATTACH=full]193597[/ATTACH] [ATTACH=full]193604[/ATTACH] [/QUOTE]

Verification