Discussion in 'other anti-malware software' started by andyman35, Mar 24, 2010.
You can't go wrong with OA, it's a great pgm as well.
Well, I wish to know definitely a thing about version 4, because Ididn't yet installed it: I was waiting for the next version release, but I'm bored to wait for.
The current version, if I disable the sandbox and use Defense + in the higgest level, the protection is the same than 3,14 ? I read here and in their forum, but I would want to be sure.
currect, just disable the sandbox and set the config to proactive setting.
You may want to select to make rules for safe applications in the Firewall and Defense+ settings, otherwise there will not be much shown in the Security Policies which may seem different.
Thanks to all.
Don't forget to remove Allow all outbound connections in the global rules if you wish v4 to be the same as v3.14.
Thanks. Anyway when I change HIPS or only the version I check up all the configuration and the settings.
I'm trying to get my setup as light as possible, though I still see cfp.exe showing up in ProcMon. How much does D+ actually help when you got the Sandbox enabled for all new files, including those that are signed as well?
the D+ detects is the program will need admin rights or not. and if it does then you get a popup.
but i think you will need D+ to use the sandbox. (i think)
Successfully turned off without affecting the Sandbox. Running SRP so don't think I need that kind of monitoring on my machine.
Is there any way to trust any application which is not identified by comodo coz whenever I execute SD D+ always pops up and say that Shadow Defender is unidentified and there is no way to tick on "Always trust the publisher of this file" option
add them to your safe file list or to the trust vendor list.
but for the trusted vendor list the app needs to be digitally signed if not then it cant be added to the trusted vendor list.
Referring to this and your attachment, I'd guess the file doesn't have a signed vendor for some reason, otherwise you would be able to remember the answer for that prompt.
Have tried using My own Safe file now working perfectly
Another thing comodo still has to look at their AV part it produces alot of FP, last night I scanned my portable drive with comodo and it detected MD v2.6 (beta1 and beta2) as Heur.Suspicious