Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Look who's talking
Message
From
31/01/2006 03:16:15
 
 
To
All
General information
Forum:
Politics
Category:
Other
Title:
Look who's talking
Miscellaneous
Thread ID:
01091784
Message ID:
01091784
Views:
32
So I installed Kerio personal firewall along with Zone Alarm and here is the result:


ZA) When I started ZA (latest ver) Kerio PF reports that the ZA TrueVector service tries to connect to;

1) 208.185.174.66 on port 80/http, (I tell Kerio to deny it)
2) then to 196.33.166.200 on port 80/http, (I tell Kerio to deny it)
3) then to 208.185.174.65 on port 443/https/SSL, (I tell Kerio to deny it)

Thereafter ZA True Vector service is trying to connect to IP #3 every few minutes or so, maybe every 10 or 15 minutes. I tell Kerio PF to deny it just to see what will happen. ZA seems unaffected by the denials so far.

I dont think these are the ZA update IP address' because "check for updates" was off. When I tell ZA to check for an update manually it tries to connect to 208.185.174.52 on port 80/http (different IP from above).

I could put a sniffer on it to see what its trying to send/receive but I'm not that motivated right now :)


KPF) When I started Kerio PF ZA reports various activities. ZA did also report that Kerio PF wanted to connect to the DNS server which I allowed in order to see what it would do but it didnt try another connection after that to any other IP (so far :). This is after a couple of hours of monitoring.

My opinion fwiw - I have always been a fan of ZA but Kerio looks extremely good with many comparable features (and some others) and good user interface. And the price is excellent as well; US$15. I dont like the smoke currently around the ZA controversy and Kerio does not appear to be making internet connections whereas ZA definitely does (for purposes unknown to me).
In the End, we will remember not the words of our enemies, but the silence of our friends - Martin Luther King, Jr.
Next
Reply
Map
View

Click here to load this message in the networking platform