VistaFirewallControl wrote:Using VFC definitions you can just create a MYZONE with a MYRULE set to your IP/port pair in the Zones tab (the repository). Then you can apply the entire MYZONE to an application or the MYRULE separately to any repository’s zone or an application’s zone directly by a single click. Undoubtedly there is no need to create the entire zone each time.
But that rule set called "MYZONE" and the "MYRULE" would contain just a certain set of IP-Addresses and Ports that will not fit for all my applications, right? So I still would need a single rule set (aka "zone") for most of my application, for example:
For my mailclient, I want to allow connections to 127.0.0.1 and 1.2.3.4:25 only. That is one rule set
For my browser, I want to allow connections to 127.0.0.1 and *.*.*.*:80 only. That is one more rule set
For my PDF-Reader, I want to allow connections to 127.0.0.1 and 6.7.8.9:8080 only. That is another rule set
And so on.
This is not very convenient.
VistaFirewallControl wrote:Using VFC definitions zone is a set of rules, so you can add multiple rules to a zone and have multiple rules set to an application. “Add from repository” button (Edit Zone dialog) makes easy new rule distribution. FYI: LocalHost enabling rule is already set to almost any predefined zone.
Sure, it is doable, but very annoying to always have to specify a "zone" first just to bundle up some rules. Most of the times, rule sets ("zones") are application specific and can not be reused anyway.
To put a long story short: after using VFC for a while I think it is a very nice approach to just offer a better interface into Vistas firewall module, but it would be much better if it would reflect the full flexibility of the Vista firewall module.
But hey, that is just my opinion!
