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: 1101007" data-attributes="member: 67091"><p>Hi [USER=91306]@wat0114[/USER],</p><p>Thank you.</p><p>But IMHO what you suggest is a partial and inefficient patch:</p><p></p><p>Some time ago, when I used Comodo for a few years, I did the same as you did, I customized as much as possible as many executables as possible. And considering that Comodo does not allow to do that, I had to invest months, it was a colossal work, one by one I manually customized as much as I could customize. The problem, as I anticipated, is that with time the executables, paths, IPs etc etc etc... change and the work becomes unfeasible.</p><p></p><p>It is not only a problem of investing tons of time, this approach also demands a knowledge that not even advanced users are used to have. It was just looking for that help, that I met the developers of other firewalls, and participants at MT who are veteran geniuses in firewall issues in general. I learned with them that these firewalls on the market are not only free, but they are maintained (updates/upgrades), have their own kernel, and the GUI is millions of times better than Comodo, allowing customization of Windows Services, Svchost etc etc etc... without having to do the titanic manual work that has to be done in Comodo.</p><p></p><p>But as I said, not even a customization in Comodo is a solution, because 20 years ago many executables began to use Svchost for comms, and with Comodo default settings the Svchost is considered “safe”, so absolutely nothing prevents a malware to use Svchost for comms. And even if you customize the Svchost (as you did in your post), at Comodo it can only be done in a generic way, for example, a simple “allow” “port: 53” (necessary for DNS) opens all comms for any malware.</p><p></p><p>Conclusion, Comodo customization demands a colossal work, it is totally partial, unusable because executables/IPs/etc change every week, and even customized, any malware can use comms with the most powerful Comodo customization.</p><p></p><p>Considering the existence of Windows Firewall and so many other free and modern firewalls on the market, it simply does not make sense to use Comodo, because it is old, abandonware, without updates/upgrades, full of unfixed bugs, and unable to make real customizations.</p></blockquote><p></p>
[QUOTE="Decopi, post: 1101007, member: 67091"] Hi [USER=91306]@wat0114[/USER], Thank you. But IMHO what you suggest is a partial and inefficient patch: Some time ago, when I used Comodo for a few years, I did the same as you did, I customized as much as possible as many executables as possible. And considering that Comodo does not allow to do that, I had to invest months, it was a colossal work, one by one I manually customized as much as I could customize. The problem, as I anticipated, is that with time the executables, paths, IPs etc etc etc... change and the work becomes unfeasible. It is not only a problem of investing tons of time, this approach also demands a knowledge that not even advanced users are used to have. It was just looking for that help, that I met the developers of other firewalls, and participants at MT who are veteran geniuses in firewall issues in general. I learned with them that these firewalls on the market are not only free, but they are maintained (updates/upgrades), have their own kernel, and the GUI is millions of times better than Comodo, allowing customization of Windows Services, Svchost etc etc etc... without having to do the titanic manual work that has to be done in Comodo. But as I said, not even a customization in Comodo is a solution, because 20 years ago many executables began to use Svchost for comms, and with Comodo default settings the Svchost is considered “safe”, so absolutely nothing prevents a malware to use Svchost for comms. And even if you customize the Svchost (as you did in your post), at Comodo it can only be done in a generic way, for example, a simple “allow” “port: 53” (necessary for DNS) opens all comms for any malware. Conclusion, Comodo customization demands a colossal work, it is totally partial, unusable because executables/IPs/etc change every week, and even customized, any malware can use comms with the most powerful Comodo customization. Considering the existence of Windows Firewall and so many other free and modern firewalls on the market, it simply does not make sense to use Comodo, because it is old, abandonware, without updates/upgrades, full of unfixed bugs, and unable to make real customizations. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
