I just wanna reply to the post by webbie146 here
Sure if you need another quote I can provide it, but I think that was quoted enough already
Anyway … There were couple of LOLs posted as a responses
I do not accept
, but I can understand that, cauz Seany007 is a blind lover of Comodo Suite & he can express his love as usual to whatever Comodo is developing
At the same time the “LOL” reaction by Melih - CEO of Comodo is really sad
Firstly, the OP described some use of Comodo in order to cheat, which is not a plausible thing in the first place… no LOL’s here according to my taste
Then, do you really have office.exe application on your PCs?
Those who laughing out loud & other who are not - please confirm
webbie146, can you post (screenshot or whatever) of office.exe Properties? and/or VirusTotal link analyzing that file?
Thing is - I never had that particular App using practically all flavours of MS Office: currently 2003 Pro; 2007 Enterprise; and Office 2010 Pro
Just use “Google is your Friend” & find out what office.exe can be… hmmm…
… but then… let’s assume that the office.exe mentioned in that fairy tale by OP is a legit App by MS that I’m not aware of
In this case it’s something similar to soffice.exe that I am using as well – (Open source Office Suite) , which is a host Application for the any “Office” Apps. Right?
You are saying that you blocked that one by mighty Comodo & after all you were able to launch Word.
Mainly, it doesn’t matter that you’ve got an empty <>.doc file being opened – what it means that the security that are you using (“Why I use Comodo IS”) failed big time, because the Child Process of the supposed Parent process you’ve just blocked was fired anyway.
That issue was discussed previously few if not many times already.
So if that is that’s case do you still think that the security you are using is up to shape?
… and for those who are still laughing – please test
That is not a laughing matter … just a simple shame & pity in any case