My last firewall is Outpost. I also know Zone Alarm (too simple) ad CoreSecurity (too detailed to be handy, is almost a debugger!). I also know Ashampoo and many others.
I was giving a try to Comodo. This is my opinion at a first glance.
I see these problems (maybe I’m wrong):
When Comodo alert for an inbound/outbound of an application on a specific port, the rule is set ANY on address/ports. This is equivalent to trusted application on other firewalls. This is not very good. :-[
In the case 1, if you try to edit the rulee (e.g. Outlook port 25), if the OL try to exit on other ports (e.g. 80), Comodo alert “Comodo is trying to exit on port 80” correctly but if you say “Yes is right, remember”, Comodo invalidate the limit of port 25 deleting that rule or in other cases creating a new rule that say “Go wherever you want!” (ANY for address/ports). This is even still worst than case 1 because destroy security without advice! :-[
So, I can’t make rules based on ports unless I decide to never say “remember” if a Comodo alert arise (because if I do, that could change existing trimmed rules).
If on the contrary I want to create limitation with specific rules (e.g. Outlook not able to exit on port 80) I encounter another problem: rules priority. What Do I mean? Let’s say I accept the auto-rule of Outlook any/any. I create a new rule where OL is blocked on destination Any, port 80. Until this rule stay on top of OL rules it works, BUT, if you touch manually or automatically another rule of OL, this lock on port 80 stop working because the other rules come first.
Related to point 4, to make the lock rule be on the top of other rule of that application, the only way is touching (open/save) all the other rules (the touched go bottom). There are not arrow like those in
security-network monitor (move up/move down). It should be simple to implement and very useful to have.
In other word, at a first glance it looks manually unmanageable.