Comodo Firewall Pro V3 Beta 3 Released

Just a heads up for you firewall testers. From user input on the forum it sounds like it went through some drastic changes in the interface and some more security parts added such as ddos protection which is not active yet. And an mode for installations.

"Installation Mode" (which I haven't used yet, but am getting ready to try...) is the much-sought-after means of installing an application without the need to disable the HIPS module. The need for this has been discussed, and Comodo has listened. The idea is that during the installation of applications (that you are intending to install) you don't want all the popups of having the HIPS on, but you also don't want to completely disable the HIPS for obvious security reasons.

Click to expand...

Post what you think if your testing.

The remember checkbox has been set to ticked by default in this version, say what you think about it...higher risk...easier use?

We would like to announce the availability of the COMODO Firewall Pro 3.0.9.229.
There are many fixes and improvements in this release. Here are a few of them :

Previous configurations exported are not compatible with this one because of the major arhitectural changes. So please try clean install only.

Major changes
---------------------------------------------
1 - Summary section has been finalized
2 - Introduced 2 new modes for the Defense+ : "Installation Mode" and "Clean PC Mode"
3 - Introduced "Pseudo-COM" interface protection : which protects priviledge escellation and other serious operaing system services e.g. service control manager
4 - The Defense+ now learns during the booting and related BSOD(SESSION_INITIALIZATION_FAILED3) bug has been fixed
5 - Configuration Import/Export windows has been redesigned
6 - Many Vista and x64 based bugs fixed
7 - Defense+ Common Tasks section has been redesigned
8 - Firewall Stealth Logic has been slightly changed to improve compatibility with various advanced network confiurations
9 - Automatic detection of new private networks added

Known Issues:

1 - Firewall DoS protection is not active right now
2 - Tips are not active right now
3 - The default configuration does not contain all critical resources e.g. registry keys, COM interfaces etc.
4 - There are compatibility issues with some other security products waiting for investigation
--------------------------

i dont know it coz i use kaspersky internet security 7
but if i use antivir premuim i will use comodo firewall with it coz i like to try comodo firewall and i will make test for the firewall from this sitewww.firewallleaktester.com

i dont know it coz i use kaspersky internet security 7
but if i use antivir premuim i will use comodo firewall with it coz i like to try comodo firewall and i will make test for the firewall from this sitewww.firewallleaktester.com

Click to expand...

Should pass all tests. The current version 2.4 passes 95% of the tests so with the added HIPS it should pass all.

Does Comodo 3 allow for easy changes from a trusted network to one that is not trusted? With Comodo 2.4 this is a pain and must be done manually. (Zone Alarm and the built in Vista FW handle this issue very well, for example.)

Does Comodo 3 allow for easy changes from a trusted network to one that is not trusted? With Comodo 2.4 this is a pain and must be done manually. (Zone Alarm and the built in Vista FW handle this issue very well, for example.)

Ok the new CFP has HIPS. So I have ThreatFire installed which is also a HIPS, right? I've heard that it's not a HIPS at all and is something else. Anyway so my question is if ThreatFire is NOT a HIPS then should I leave ThreatFire installed and will I be ok if I allow CFP's HIPS to be active? Are these two the same techologies or what? By the way I'm very happy with TF so if TF is indeed a HIPS and considering that CFP has HIPS. Which is one is stronger of the two? Which should I keep. Also just to make mention I don't plan on installing CFP until it goes final.

Ok the new CFP has HIPS. So I have ThreatFire installed which is also a HIPS, right? I've heard that it's not a HIPS at all and is something else. Anyway so my question is if ThreatFire is NOT a HIPS then should I leave ThreatFire installed and will I be ok if I allow CFP's HIPS to be active? Are these two the same techologies or what? By the way I'm very happy with TF so if TF is indeed a HIPS and considering that CFP has HIPS. Which is one is stronger of the two? Which should I keep. Also just to make mention I don't plan on installing CFP until it goes final.

Click to expand...

Threafire i am guessing is what used to be cyberhawk? If it is than it is not a HIPS but behaviour blocker. A HIPS is much stronger and secure. If your not used to seeing alerts for every little thing than keep threatfire and disable the defence+ of cpf. I used to use cyberhawk with comodo 2.4 until i noticed comodo had the same behaviour blocking as cyberhawk so you might as well uninstall threatfire if you choose to install cpf 3.