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
Browsers
Web Extensions
[Updated 29/12/2018] Browser extension comparison: Malwares and Phishings
Message
<blockquote data-quote="Windows_Security" data-source="post: 790850" data-attributes="member: 50782"><p>Thanks, or the link.</p><p></p><p></p><p>Feel free to believe the blog of the VB-editor, but it is [a seven character word which will be moderated and starts with a B and ends with a T]. To conclude with the author of the VB-blog: yes breaking security integrity for security sake COULD (in theory) improve security, that is true. It is just not likely that only goodware uses this compromise and the chance of running into a risky web interaction of the security unaware users even decreases the likely hood of this comprise paying out well.</p><p></p><p>The editor uses the same arguments HIPS/Security Vendors used when Microsoft stopped allowing kernel patching in 64-bits systems. It is a known and never ending discussion in security forums, simular to kernel patching and Sandboxie breaking the integrity of the Chrome sandbox on Windows. My take is clear on this. When AV-vendors should not compromise HTTPS, neither Ad & Tracking blockers and Parental Control programs should not do this either.</p></blockquote><p></p>
[QUOTE="Windows_Security, post: 790850, member: 50782"] Thanks, or the link. Feel free to believe the blog of the VB-editor, but it is [a seven character word which will be moderated and starts with a B and ends with a T]. To conclude with the author of the VB-blog: yes breaking security integrity for security sake COULD (in theory) improve security, that is true. It is just not likely that only goodware uses this compromise and the chance of running into a risky web interaction of the security unaware users even decreases the likely hood of this comprise paying out well. The editor uses the same arguments HIPS/Security Vendors used when Microsoft stopped allowing kernel patching in 64-bits systems. It is a known and never ending discussion in security forums, simular to kernel patching and Sandboxie breaking the integrity of the Chrome sandbox on Windows. My take is clear on this. When AV-vendors should not compromise HTTPS, neither Ad & Tracking blockers and Parental Control programs should not do this either. [/QUOTE]
Insert quotes…
Verification
Post reply
Top