@andy, I just wanted to add a bit of humor with that little story. I truly value your opinion and your work, as well as the contributions from others here who have far more experience than I do in web security. You've all helped me tremendously on this forum (MalwareTips) to better understand and improve my limited knowledge on the subject.@Halp2001,
Look at the above post.
I do not neglect the Comodo security flaws, but rather show that the proposed solution does not guarantee more security.
Another problem can be usability bugs, but this was skipped in your analogy.
In my analogy, the bugs are not so important for Bob, as his way of using skis avoided the problems that happened for other users.
But I was give a minimal and supporting role!!! I am not happy! I should the the main character@andy, I just wanted to add a bit of humor with that little story. I truly value your opinion and your work, as well as the contributions from others here who have far more experience than I do in web security. You've all helped me tremendously on this forum (MalwareTips) to better understand and improve my limited knowledge on the subject.
I'm genuinely grateful to those who test security software and share their findings with the community, and also to those who offer well-reasoned opinions. But sometimes, you all dive into discussions that leave me a bit lost—especially when the language gets super technical for a humble mortal like me.
But I was give a minimal and supporting role!!! I am not happy! I should the the main character![]()
@Andy Ful
You see, Alice is that brilliant, charismatic piece of proprietary software with a few... let's call them "undocumented features." Her developers insist the gaping security holes are just "charming quirks." "That's not a vulnerability," they say with a dismissive wave, "it's a feature that adds character! You just need to use it correctly." Users who complain are just holding it wrong. Alice is perfect, you see, and any perceived flaws are simply a failure of your imagination.
Then there's Bob. Bob is the earnest, open-source project. He lives and breathes for user feedback. Every vulnerability report is a love letter, every pull request a sonnet. He patches, he updates, he evolves. He's a fortress of community-driven security, a testament to the power of listening to your users. He's everything Alice isn't.
And that's the punchline you've so cleverly stumbled upon.
We all thought they were opposites, two warring philosophies of development. But it was a long con. Alice's "vulnerabilities" were never flaws, they were encrypted love notes, backdoors left open only for Bob. And Bob, with his army of well-meaning users, wasn't just patching his own code. He was crowdsourcing the perfect key.
Every "user recommendation" he implemented was another piece of the puzzle, another step toward exploiting Alice's "charming quirks." He let us, the community, do the heavy lifting. We were the unpaid QA team for their hostile takeover of reality.
So when they finally merge, it won't be a simple connection. It will be the ultimate patch. Bob, using the very tools we gave him, will exploit Alice's "features" on a global scale. They won't just be a secure couple, they'll be a single, terrifyingly efficient entity. The beautiful, flawed, "it's-not-a-bug" framework merged with the impenetrable, user-hardened fortress.
They're not just getting together. They're releasing the final, stable version of our world. And we, the users, just gave them a 5-star rating on the way out.
You want me to check over 100 bugs and report each of them on Comodo forum and experience the same Comodo Staff feedback which I have been getting and reading for years on the Comodo forum saying no more than things like "We have send it to our team", "Thank you for reporting", "May I know your CIS version", "The team is working on it", blah, blah, blah, etc.Your criticism follows from "dark" period of Comodo management a few years ago (no new versions for a long time).
Another reason is the lack of clear information about removing bugs, even when some silent fixes were confirmed.
Only time can show if your high criticism is justified. After six months, there is no evidence for that (may be too short period).
People who use CIS 2025 are far less sceptical.
Your arguments would be much more convincing if you could use/test Comodo by yourself (as some others and I did).
Who's who?But I was give a minimal and supporting role!!! I am not happy! I should the the main character![]()
Bob took Alice outI haven't read through all of the posts yet, but I'll pick up on the example with the skiers
I refuted your claim that Comodo had fixed 40 old bugs.@Pico,
I refuted most of your posts, but you did lose your cool.
Your posts were noted, even if not compatible with rule 2.
Thanks for helping me find the bug lists related to CIS 2025.
@AndyFul and others who know more than I do, based on what you have been analyzing and discussing about CIS, I have devised this configuration strategy to use only the Comodo Firewall component. In an environment where FUD (Fully Undetectable) malware is constantly evolving to evade modern security layers, a traditional defense is no longer sufficient. This guide presents a hybrid strategy that combines next-generation technologies with local containment and operating system hardening, based on tools developed by Andy Ful and configurations recommended by experts such as CruelSister and Vitao Tek.
I would like to know what the experts think about this, as your help is very valuable to me, and I thank you in advance. I hope I have not strayed from the topic of this thread, and if I have, it was not my intention, for which I apologize.
View attachment 291374
You seem to haven't found the List Of Bugs with the Comodo Staff FIXED labels on some bugs.
If they can't handle Comodo, then how they gonna handle a puppy - a living thing?Yikes! Some here have way, way, way too much time on their hands!
Perhaps time would be better served by adopting a puppy...
If they can't handle Comodo, then how they gonna handle a puppy - a living thing?
View attachment 291514