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: 1101058" data-attributes="member: 67091"><p>Comodo by default considers all Windows Services, all SVCHOST and an endless list of other files to be "safe"/"trusted".</p><p></p><p>A "safe"/"trusted" file in Comodo, inside or outside of a sandbox, will always have free comms. Any (irresponsible/immoral) fanatic can confirm this, by observing that tons of his files right now are using comms through SVCHOST.</p><p></p><p>It is important to remember that Comodo's "safe/trusted" label is an arbitrary list that is outdated (not updated in the last 15 years). So, at Comodo, hundreds of files are considered "safe"/"trusted" by default.</p><p></p><p>The problem is unsolvable because Comodo does not allow customizations of Windows Services, SVCHOST and tons of other files. It is not a configuration problem, but rather a problem with the deprecated old Comodo model.</p><p></p><p>Therefore, as another MT member rightly stated: "<strong><em>Svchost is a nice comms backdoor for every running app, background process or service</em></strong>". Or in my own words: "<strong><em>Comodo Firewall is a placebo</em></strong>".</p></blockquote><p></p>
[QUOTE="Decopi, post: 1101058, member: 67091"] Comodo by default considers all Windows Services, all SVCHOST and an endless list of other files to be "safe"/"trusted". A "safe"/"trusted" file in Comodo, inside or outside of a sandbox, will always have free comms. Any (irresponsible/immoral) fanatic can confirm this, by observing that tons of his files right now are using comms through SVCHOST. It is important to remember that Comodo's "safe/trusted" label is an arbitrary list that is outdated (not updated in the last 15 years). So, at Comodo, hundreds of files are considered "safe"/"trusted" by default. The problem is unsolvable because Comodo does not allow customizations of Windows Services, SVCHOST and tons of other files. It is not a configuration problem, but rather a problem with the deprecated old Comodo model. Therefore, as another MT member rightly stated: "[B][I]Svchost is a nice comms backdoor for every running app, background process or service[/I][/B]". Or in my own words: "[B][I]Comodo Firewall is a placebo[/I][/B]". [/QUOTE]
Insert quotes…
Verification
Post reply
Top
