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: 1101043" data-attributes="member: 67091"><p>All unfixed bugs and design flaws in Comodo follow a consistent pattern with a similar explanation:</p><p></p><p>Twenty years ago, blockers like "deny-all" and "zero-trust" thrived in the market, competing with major players by effectively blocking viruses and malware that others did not, especially some zero-day attacks.</p><p></p><p>However, over time, new technologies emerged, and major players evolved by incorporating modern capabilities. Consequently, blockers gradually became obsolete, as it makes no sense to use a user-dependent blocker when there are excellent, modern, free antivirus solutions that automatically identify and remove malware.</p><p></p><p>Twenty years ago, Comodo had the chance to evolve and adapt to modernity. Unfortunately, its mediocre CEO (hated by his employees) decided that the CIS model would no longer be developed. No new features were added, and the software entered into "survival" mode (no maintenance, no updates, nor upgrades etc).</p><p></p><p>This explains why Comodo currently has hundreds of unfixed bugs and why the CEO, staff, and even Comodo fanatics publicly acknowledge these bugs and accept that they will never be fixed.</p><p></p><p>It also explains why the Comodo model is frozen in time, failing to incorporate new technologies or features. It continues to operate using a dangerous list of "known"/"unknown" files for allowing/blocking, an arbitrary list that hasn't been updated for 15 years. Due to the lack of updates, the number of "unknown" files for Comodo is now endless, leading to countless false containerizations and making usability impractical on Windows 11 (which is hyper-connected and requires constant synchronizations with other devices). For those who don’t understand, Comodo essentially becomes a dummy blocker; it does not identify viruses or malware but merely allows/blocks files based on an outdated list of "known"/"unknown".</p><p></p><p>The same logic applies to the Firewall. It is stuck in the past (20 years ago) when Windows Services or Svchost were not used by other files and could be considered "safe." This is why Comodo currently does not allow customizations for Windows Services, Svchost, and many other vulnerable files. In practice, Comodo Firewall serves as a placebo because, as you accurately put it: "i<em><strong>t is </strong></em><strong><em><strong><em>a </em></strong>nice comms backdoor for every running app, background process, or service</em></strong>".</p><p></p><p>In summary, Comodo represents a pattern of poor business decisions made 20 years ago, resulting in the accumulation of hundreds of unfixed bugs and freezing the Comodo model in time. Today, its blocker is inefficient, its firewall is a placebo, and the rest of the modules are garbage. Comodo has failed to adapt to modernity and can be considered an abandonware.</p><p></p><p>This explains why Comodo's market share is negligible, its revenues are insignificant compared to its competitors, and its staff consists of a small group of dissatisfied employees. The company and its model are on the brink of extinction. In this context, fixing bugs is futile, as the Comodo model is doomed. Therefore, discussing unfixed bugs or design flaws endlessly serves no purpose.</p><p></p><p>The only remaining action is to combat the irresponsibility and immorality of Comodo and its fanatics, in order to prevent readers from being misled and deceived by these Comodo-garbage-threads.</p></blockquote><p></p>
[QUOTE="Decopi, post: 1101043, member: 67091"] All unfixed bugs and design flaws in Comodo follow a consistent pattern with a similar explanation: Twenty years ago, blockers like "deny-all" and "zero-trust" thrived in the market, competing with major players by effectively blocking viruses and malware that others did not, especially some zero-day attacks. However, over time, new technologies emerged, and major players evolved by incorporating modern capabilities. Consequently, blockers gradually became obsolete, as it makes no sense to use a user-dependent blocker when there are excellent, modern, free antivirus solutions that automatically identify and remove malware. Twenty years ago, Comodo had the chance to evolve and adapt to modernity. Unfortunately, its mediocre CEO (hated by his employees) decided that the CIS model would no longer be developed. No new features were added, and the software entered into "survival" mode (no maintenance, no updates, nor upgrades etc). This explains why Comodo currently has hundreds of unfixed bugs and why the CEO, staff, and even Comodo fanatics publicly acknowledge these bugs and accept that they will never be fixed. It also explains why the Comodo model is frozen in time, failing to incorporate new technologies or features. It continues to operate using a dangerous list of "known"/"unknown" files for allowing/blocking, an arbitrary list that hasn't been updated for 15 years. Due to the lack of updates, the number of "unknown" files for Comodo is now endless, leading to countless false containerizations and making usability impractical on Windows 11 (which is hyper-connected and requires constant synchronizations with other devices). For those who don’t understand, Comodo essentially becomes a dummy blocker; it does not identify viruses or malware but merely allows/blocks files based on an outdated list of "known"/"unknown". The same logic applies to the Firewall. It is stuck in the past (20 years ago) when Windows Services or Svchost were not used by other files and could be considered "safe." This is why Comodo currently does not allow customizations for Windows Services, Svchost, and many other vulnerable files. In practice, Comodo Firewall serves as a placebo because, as you accurately put it: "i[I][B]t is [/B][/I][B][I][B][I]a [/I][/B]nice comms backdoor for every running app, background process, or service[/I][/B]". In summary, Comodo represents a pattern of poor business decisions made 20 years ago, resulting in the accumulation of hundreds of unfixed bugs and freezing the Comodo model in time. Today, its blocker is inefficient, its firewall is a placebo, and the rest of the modules are garbage. Comodo has failed to adapt to modernity and can be considered an abandonware. This explains why Comodo's market share is negligible, its revenues are insignificant compared to its competitors, and its staff consists of a small group of dissatisfied employees. The company and its model are on the brink of extinction. In this context, fixing bugs is futile, as the Comodo model is doomed. Therefore, discussing unfixed bugs or design flaws endlessly serves no purpose. The only remaining action is to combat the irresponsibility and immorality of Comodo and its fanatics, in order to prevent readers from being misled and deceived by these Comodo-garbage-threads. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
