Vista/7 outbound control - not really that hard

[itman]

I see camps for both WFN & WFC in here.

I really liked WFN. Mainly because the developer actually was interfacing with the Vista/WIN 7 firewall API. When a rule was created using WFN, it was actually added as a rule to the WIN firewall rules.

My main issues with it is it was buggy as much of this "part-time" developed software is. The developer has a full-time day job in IT and worked on it in his spare time. I also notice that there haven't been any updates to it since May so I don't know if he is actively supporting it anymore.

[adrenaline7]

I have used WFC and liked it. It used maybe 60mb ram but I have 6gb and it didn't seem to use a lot of cpu or disk so performance wise I noticed no impact. I like that it has a pop up for a blocked program. I went back to Windows FW w/ Advanced Security. I don't get pop ups for blocked programs but I tightened it down as much as I could and will just keep it simple and stick with it.

[itman]

I might just try WFN again. I just noticed that Khan added an option to WFN to bypass WIN services detection which is exactly what I have want. This way Vista/WIN 7 is dynamically handling services via WSH.

Again I do have reservations with WFN because it is using the WIN 7 firewall API. As such, your trusting WFN not only properly handle inbound and outbound traffic but to not "add" anything that is not on the "up and up."

Note that I beleive WFN is an unsigned app.