Yes disabling HIPS has been one of her suggested tweaks going back years, and again also recently posted here in a recent video.Yes, and in her videos she always has HIPS disabled. I think it's one of her tweaks as well.
Yes disabling HIPS has been one of her suggested tweaks going back years, and again also recently posted here in a recent video.Yes, and in her videos she always has HIPS disabled. I think it's one of her tweaks as well.
You just like to go onto forums to bash Comodo without any proof. Then call the Comodo CEO a liar based upon, what again?... Trident's nonsense. OK. We all get it now.I would but again, I’m not interested in mediocre products to waste my time really…
What do I have to prove? I never said that Comodo was bulletproof. Comodo itself said it is bulletproof. Why would I have to prove what Comodo said?I am awaiting your proof my dear @Oerlink.
I already did that. I linked the AVLab tests. AVLab tests are well-designed and credible. You are the only one who makes up complete nonsense in an attempt to discredit them.Prove to all of us that Comodo’s design is secure.
Link at least one study where Comodo has been tested in depth (not against 30 executables that Webroot will detect too), I am talking about a system analysis and design test or simply said - pen-test that concludes Comodo is secure.
Or provide documentation from Comodo website that explains the product architecture and analyse this documentation bit by bit.
It is wonderful that you believe such nonsense. You have quite the imagination. Have you ever thought of a career with "Trident Story Hour" at your local libraries?This is how you will prove that Comodo is indeed still secure for general usage. Bear in mind effective in detection/protection/disinfection does not equal SECURE, stable and fit for the purpose.
Comodo has proven itself great protection all by itself.If you manage to prove you are right by showing the relevant studies and conclusions
I'm not familiar with neither the bugs nor custom configurations recommended by others. I only know if the software hasn't been updated in 2 years, then it should be a red flag.agree agree, but as I understand @cruelsister CF tweaks she disables HIPS and apparently HIPS is where the bugs are. I don't read comodo forum, & not currently running CF here. just sayin'
sure agree a "red flag" meaning make a more considered, more researched judgment about running it knowing that it hasn't been updated for 2+ years. some with strong reputation here say it's still solid protection despite lack of recent updates. I am not running it but like to read reasoned feedback from users that are running it.I'm not familiar with neither the bugs nor custom configurations recommended by others. I only know if the software hasn't been updated in 2 years, then it should be a red flag.
There's someone out there running PCTools ThreatFire on their XP system right now.
Melih should tell developers to remove HIPS then change version number to 14.2023 and then leave it at that.sure agree a "red flag" meaning make a more considered, more researched judgment about running it knowing that it hasn't been updated for 2+ years. some with strong reputation here say it's still solid protection despite lack of recent updates. I am not running it but like to read reasoned feedback from users that are running it.
Or deny, and then wonder why something isn't working. Been there, which is why when Comodo is on this machine, I disable HIPS.Melih should tell developers to remove HIPS then change version number to 14.2023 and then leave it at that.
The HIPS should have never been there in the first place. Home users do not know what "Access to COM Object" or "Writing to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Safer\CodeIdentifiers" HIPS alert means. The home user just keeps clicking "Allow"... "Allow"..."Allow"..."Allow"
lol
Why? Because everybody knows that home users do not understand HIPS alerts - or most any security notification for that matter?You seem to have contempt for home users.
So every home user is a non-expert in this area according to you. You, for someone not using Comodo, 'seem' to know everthing about Comodo and their users.Why? Because everybody knows that home users do not understand HIPS alerts - or most any security notification for that matter?
Because home users cannot handle alerts is the very reason security software publishers disable HIPS and configure other features to NOT generate alerts by default. That is their "optimized default configuration" = no alerts.
Try harder.
He is a bit of a know it all. Also pretends to have spoken to Comodo staff and what not! He has already lost all credibility among normal folks except the fanboys/girls who worship the product as much as he does.So every home user is a non-expert in this area according to you. You, for someone not using Comodo, 'seem' to know everthing about Comodo and their users.
You like to put yourself on a pedestal, high above the rest.
Oh Holy Grail.
I never said that. How could you even interpret that is what I said? The vast majority of users cannot properly handle alerts. That is why companies like Kaspersky, ESET and Emsisoft "optimize" their products so that, by default, there are no alerts for the user to respond to. It is an industry-wide practice. It is the very reason that Comodo configures HIPS to be disabled by default! lolSo every home user is a non-expert in this area according to you.
Alerts and how users can or cannot respond to them is not specific to Comodo. Plus I never said I know everything about Comodo users. It is really weird that you could even make that interpretation from what I posted.You, for someone not using Comodo, 'seem' to know everthing about Comodo and their users.
Why? Because I am stating the facts? What is wrong with you?You like to put yourself on a pedestal, high above the rest.
Oh Holy Grail.
Do you actually believe that I care what you or anyone else thinks?He has already lost all credibility among normal folks
If I am lying, then where is your proof? Oh wait, you don't have any. Even if I am lying about talking to Haibo Zhang and others, the fact doesn't change - Comodo is not fixing those bugs. It has had 12+ years to do so and it has not.Also pretends to have spoken to Comodo staff and what not!
Btw I can’t establish if you are defending the product or bashing it - it seems like the latter to me. Do you just regularly go around on forums to bash competitive products is my first question here.f I am lying, then where is your proof? Oh wait, you don't have any. Even if I am lying about talking to Haibo Zhang and others, the fact doesn't change - Comodo is not fixing those bugs. It has had 12+ years to do so and it has not.![]()
He just elegantly avoids talking about it…@Trident - your investigations are spot on! @Oerlink has been previously banned from this thread. He has had arguments with the wonderful @danb who I respect immensely - he stalked him based on that thread as a person called JT on wilders - works for Appguard (I think).
I am sure he will come around and debate all of this (he did not read things properly before). Pointless arguing with someone who knows in their head that they are right and live off emotionally laden discussions! But, love your investigative journalism here @Trident - kudos![]()
Regardless what “users with strong reputation say” it is considered a standard practice within the whole IT industry out-of-date software to be avoided. It’s not just Comodo or Software A,B and C, it’s every package that hasn’t been updated. The same is even more true when we talk about security, as it’s an always-running app with kernel access - security holes are a recipe for disaster.I'm not familiar with neither the bugs nor custom configurations recommended by others. I only know if the software hasn't been updated in 2 years, then it should be a red flag.
There's someone out there running PCTools ThreatFire on their XP system right now.
For the passionate keyboard warrior and AppGuard employee, I will once again stress — nobody has claimed anything here. You just need a discussion (lack of anything to do in your daily life as well as social skills) and you have “assumed” we are saying Comodo is unsafe.You and the others are just making conjecture. If any of you had made a demonstrable argument, then you would have no problem getting people to agree with you. But as it stands, you've convinced no one that Comodo is unsafe.
Do we need proof to express a concern on a public forum? I didn’t know MalwareTips was the high court in Strassburg, but I am glad you have enlightened us.But it is unproven that it is unsafe, even after 2 years of no updates.
Melih says a new version is coming and bugs will be fixed and you repeatedly claim that bugs are not getting fixed. It has become evident on many occasions that you have natural language processing issues (amongst many others like megalomania), but the way I see it, it is you who indirectly calls Melih a liarI like the one repeated numerous times... "We have to assume that Melih is a liar."
You know your post history is public, right? You stated the product was unsafe "because of bugs and no updates in 2 years."We are merely exploring the possibility an outdated programme to be unsafe. Is that okay with you…?
Melih said a new version is coming. He never said that the bugs people have been talking about here will be fixed. The development team decided long ago that they will not fix certain bugs. That is why those bugs have remained on the list at Comodo forum forever. It has been stated as much on the Comodo forum. You should go read it carefully.Melih says a new version is coming and bugs will be fixed and you repeatedly claim that bugs are not getting fixed.
No, it's not. Significant portions of Windows and the Linux kernel itself have not received updates in decades. Some parts of Windows are the same code from the 1990s.Regardless what “users with strong reputation say” it is considered a standard practice within the whole IT industry out-of-date software to be avoided.
That is exactly how Windows Vista was proven unsafe - through real exploits, PoCs and other real-world compromises. Proof was provided by researchers, pentesters and users for years.Like do we need to design PoC and exploits to prove Windows Vista wasn’t safe?
How embarrassing for you. Comodo containment runs in User Mode.The same is even more true when we talk about security, as it’s an always-running app with kernel access - security holes are a recipe for disaster.
He prefers to be addressed by his first name, Melih.Also, stop calling him Melih — he is Mr. Abdulhayoglu.
Melih did not start the freemium industry. It existed long before he came along.He has pioneered the freemium industry and you’ve merely written 10 “for loops” for an unsuccessful product, 5 of which were wrong.
The product not being updated for 2 years means that it contains a collection of outdated drivers and scanning for malware, emulating (if Comodo uses emulation) as well as running malware in an outdated sandbox MAY (bear in mind I am not saying it WILL but exploring a possibility here) provide malware with more access it could normally have, simply being missed by a regular (if that’s a thing) antivirus. Once a malware is able to obtain kernel access, it could bypass a whole stack of defences.
You really like to talk and have your voice heard, but you should learn to read carefully what people are saying. Above is a quote from a post that is now suffocated under the multitude of posts you generated one way or another, or caused. I urge you to read carefully what I’ve said there.You know your post history is public, right? You stated the product was unsafe "because of bugs and no updates in 2 years."
I am extremely ashamed!How embarrassing for you. Comodo containment runs in User Mode.
Why manage risk from obsolete products?
Using obsolete products compounds two related problems:
In combination, these issues make high-impact security incidents more likely. This will include malware exploiting remotely-accessible vulnerabilities, which can have a catastrophic impact, across an entire organisation.
- 1
The product will no longer receive security updates
If developers are no longer providing security updates, this increases the likelihood that exploitable vulnerabilities will become known by attackers.- 2
The latest security mitigations are not present
Older products may lack the latest security measures, increasing the impact of vulnerabilities, making exploitation more likely to succeed, and detection of any exploitation more difficult.
When a product is no longer supported by its developer, there are limits on the measures that will be effective in protecting against new threats. Over time, new vulnerabilities will be discovered that can be exploited by relatively low-skilled attackers.
Not correct at all. Drivers do not need routine updates. You might as well call Kaspersky, Bitdefender and a bunch of other security software insecure because they have not updated their drivers in years.The product not being updated for 2 years means that it contains a collection of outdated drivers
The containment is not outdated. Nobody has demonstrated that it is unsafe. The technology itself is not obsolete nor does it need an update because Windows 11 was released.emulating (if Comodo uses emulation) as well as running malware in an outdated sandbox MAY (bear in mind I am not saying it WILL but exploring a possibility here) provide malware with more access it could normally have, simply being missed by a regular (if that’s a thing) antivirus.
All Norton drivers for example on Windows have been updated on the 14/10/22.Not correct at all. Drivers do not need routine updates. You might as well call Kaspersky, Bitdefender and a bunch of other security software insecure because they have not updated their drivers in years.