thanks to Pondus who let me know about it anyway doesn’t really matter much to me as I only run CIS firewall with Def+ (including the sandbox now) and AV of course completely deactivated. But that’s interesting. What would interest me more is how Avast sandbox would have resisted…
for once I agree with you (yes ;D ) that’s exactly what they will do + they will accuse the tester (from malware research group) of doing things the wrong way.
Well it is just as with everything, you have the optimist, that reacts to bob’s posting like I quote from there:
I’m sure it’ll be fixed soon. I also wouldn’t mind a comment from the Staff to confirm my suspicions.
I wonder how long that will be there, I know Comodo does not like to welcome critical opinion.
All that is coded, bob told me once, can be uncoded, by-passed, developers have to invest time in finding those holes and exploitable code bits, if the malcreants cannot break it as a whole, they do it in parts, this is so for all code, and this is for all software as long as a machine can render more efficiently as the coder’s brains, we stay in this rat hole, my friends, tails knit firmly together…
I and others told them from the beginning that things could jump out of the sandbox and at first they denied it and then claimed it was fixed in 4.1. I guess it wasn’t
Look like i do good great for stay away of Comodo. ;D
I hear a War that start soon. Comodo vs MRG or maybe Users vs Comodo.
lol…
Lucky Comodo he thinked to got a product of high quality. Look like no also the version was Premium im sure they will say the Complete would have block it lol.
This certificate problem is not unique to Comodo. All of the vendors have had the same things happen.
[/quote]
true, we’ve been through that before, Verisign etc…they’ve all done that unfortunately, whether they were tricked or not is another topic. Yokenny posted in the thread I started about that here, I was blaming myself Comodo and after collecting more info, I posted additional links, that might have included that one: http://www.ccssforum.org/malware-certificates.php
Yokenny must have read that, but he had to post his link again : …of course You know what Yokenny, you’re just like Comodo, you’re no better then they are…you could work for them may be they’re hiring ??? ;D
Back to topic: in the the thread Tech linked to, they’re indeed as predicted (was actually posted before my thread here but I didn’t know it) doing their best to attack the method. Comodo as usual won’t recognize anything, marking their difference here with other companies, especially Avast. I mean I’ve seen Avast recognize flaws or mistakes several times, Comodo never. For Comodo, a tester proving that Comodo has a flaw is a criminal and a malware provider himself ;D
the firewall and the HIPS there are definitely to separate from all the rest, i.e. all the crap they provide (you know, stickers, cups, flags etc… ;D ) but it’s getting harder and harder to dissociate even the very few good products from the company producing them and their behavior. I wanted to ditch CIS for ages, I did, and I’m using the firewall again…will be like that as long as I don’t find an equivalent.
I was shocked by the video.It s amazing how Comodo stood still when it was beeing flushed from the system.The example is with a rougue but lets think further ,what if the thing that “uninstalls” Comodo installs something invisible ?!
Having in mind many users install Comodo for the firewall components only i m wondering if the same file can “uninstall” Comodo when runned normal not sandboxed.
Many users do P2P to download “stuff” ,if this stuff is upgraded with this thingy we can conclude many users may be left without firewall protection in no time maybe even not knowing.
At this moment i stopped trusting Comodo totally.
Practically Comodo self protection is NULL.
So many questions when you use it and when something unistalls it completelly it stayes sillent like a dead fish.
Will you do the same when avast miss a virus that infect your computer?
Or when avast gives you a BSOD or you can’t login?
Besides high temperature discussion about Comodo, they are working on a solution (maybe a captcha or other security lock for uninstallation). Indeed, a huge problem.