What happened here? Isn´t a firewall supposed to resist against simply to be turned off by a task manager? What if some malware is doing this?
I do not use the defense +, since for that task i use SSM. Can anyone here confirm, that CFP3 is not able to protect itself against this most simple attack? I can´t believe this.
First, I advise you that you put your question in the wrong section.
About the process termination, well… Defense+ protect CFP 3, but, if you choose another program, like System Safety Monitor or EQSecure for System, you should configure your programs to protect CFP 3.
Isn´t a firewall supposed to resist against simply to be turned off by a task manager? What if some malware is doing this?
If you are referring to the fact that CFP.EXE can be shut down, you are mistaken in thinking that CFP.EXE is the firewall. CFP.EXE is merely the GUI that is used to configure and monitor the firewall processes. With a bit of further fiddling, you can kill off CMDAGENT.EXE, but the kernel level driver that does the packet filtering is still intact, ergo, the firewall is still running.
I do not use the defense +, since for that task i use SSM. Can anyone here confirm, that CFP3 is not able to protect itself against this most simple attack?
Thanks a lot. I hoped, this would be the case. I couldn´t imagine, that a exquisite firewall like CFP3 would be in fact that helpless against such attacks, but, never mind, i had to ask.