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
Security Apps
Comodo
Comodo CIS Bug fix policy
Message
<blockquote data-quote="Decopi" data-source="post: 1101126" data-attributes="member: 67091"><p>By Comodo default settings all Windows Services files, all Svchost instances, and another long list of files are considered "safe"/"trusted".</p><p></p><p>By Comodo default settings, any file labeled as "safe"/"trusted" always had, has and will have free comms.</p><p></p><p>At Comodo any sandboxed, restricted, containerized blah blah blah (whatever you want to call it), if labeled as "safe"/"trusted" then always had, has and will have free comms.</p><p></p><p>At Comodo any virus/malware can use Windows Services, Svchost instances, and any other file labeled as "safe"/"trusted" to access free comms.</p><p></p><p>At Comodo, the "safe"/"trusted" label is based on an arbitrary list (not updated in 15 years).</p><p></p><p>Therefore, Comodo Firewall always was, is and will be a placebo.</p><p></p><p>PS: The problem has no solution, because default or not default, Comodo Firewall settings don't allow the customization of Windows Services files, Svchost instances, and many other files.</p></blockquote><p></p>
[QUOTE="Decopi, post: 1101126, member: 67091"] By Comodo default settings all Windows Services files, all Svchost instances, and another long list of files are considered "safe"/"trusted". By Comodo default settings, any file labeled as "safe"/"trusted" always had, has and will have free comms. At Comodo any sandboxed, restricted, containerized blah blah blah (whatever you want to call it), if labeled as "safe"/"trusted" then always had, has and will have free comms. At Comodo any virus/malware can use Windows Services, Svchost instances, and any other file labeled as "safe"/"trusted" to access free comms. At Comodo, the "safe"/"trusted" label is based on an arbitrary list (not updated in 15 years). Therefore, Comodo Firewall always was, is and will be a placebo. PS: The problem has no solution, because default or not default, Comodo Firewall settings don't allow the customization of Windows Services files, Svchost instances, and many other files. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
