I just don't see why anybody should be discouraged from using Kerio.
Its works just as well for novices as ZA does. The extra configuration
capabilities of Kerio are optional. You don't have to mess with them
if you don't want to.
Are you telling me you are trying to use it exactly like in ZA free? You
let kerio tell you when a app is trying to connect outwards and you then
allow it to go outwards without specifying either ip address or port
number? And would a newbie know what "server" rights in ZA translates to
in Kerio terms?
That MIGHT work, altough, ZA being a application based firewall is far
more suitable for that, as compared to a rule based firewall. (I used to
think that a rule-based firewall was far superior to a app based
firewall, but I understand the former has some advantages.)
I'm not sure how you can figure out whether to allow ICMP pings, which I
think ZA handles automatically? Do you use proxomitron or something
similar? That adds another complication together with Kerio, wrongly
configured it will almost totally defeat the purpose of using a firewall
for outbound filtering.
I hope they're still as simple to set up basically though. Extra
options never hurt anybody.
It's only when it becomes required that
you mess with them that problems arise.
Unfortunately, in many cases ignorance is not bliss.
Anyway The 2 major features added are
IDS
"Application firewalling" -to guard against leak tests.
The latter is similar to what the newer Tiny (which intergretes TTT)
already has, and controls what processes can run, and what they can
spawn/open. Technically not the job of a firewall but necessary to defeat
leak tests. If you use SSM (sam-security monitor) you will have an idea
of how it works.
Not strictly necessary, but they will borther the heck out of you each
time any process starts on your computer. This is far worse since this
occurs a lot more then when any proccess merely connects outwards.
I can forsee, people just clicking yes for everything.
Aaron