spooler
@cableone.net
| reply to IGGY
Re: what's missing here?
Iggy said:
"But the first thing ZA does without asking is contact ZoneLabs for one or more of various reasons"
This action would of course be blocked when set to be blocked.
-------------------
But here's what happens on my system at every startup.
First thing out of the box, ZA contacts zone labs at one or more of the sites mentioned in your earlier post explaining that is what happens. [See capture of router log traffic]
Here's the link that said it would happen:
»Why Zone Labs software contacts Zone Labs
Interesting thing is that no alert pops up and no entry appears in the ZoneAlarm logs. [See capture of blank ZA log page]
More interesting is the program settings where the ZAClient is blocked all accross the board. [See capture of it in next post]
Also interesting is the fact that the first ZA status page is set for ZA not to contact ZoneLabs without first alerting the user and asking for permission. [See capture in next post]
There may be an explanation . . .
Does it stop me from using ZA? - no.
Does it make me wonder why ZA works this way? - yes. |
|
Snakebytes
| Thanks Spooler,
I will be re-thinking if I should renew my subscription to ZoneAlarm Pro. It is due soon.
I dont like these kind of backdoor surprises. Certainly dont want to be paying money for them. |
|
