Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 5
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 1279 times and has 4 replies Next Thread
OnePelican
Cruncher
Joined: May 23, 2008
Post Count: 5
Status: Offline
Reply to this Post  Reply with Quote 
ZA

Here is BBC news item.
Net address fix foxes web users

Lowering security settings can get ZoneAlarm users back online
Many users of the ZoneAlarm firewall have been floored by a fix to the net's addressing system.

Those hit found they could not get online after installing a Microsoft patch to close a security loophole.

Left open the flaw would have allowed malicious hackers to redirect users to fake websites, even if they typed the correct address.

Many net hardware and software firms prepared and applied patches this week to close the serious hole.

Firewall fix

The flaw in the net's Domain Name System (DNS) was discovered in March 2008 and since then many firms have been preparing patches and updates to ensure it cannot be exploited by hi-tech criminals.

On Tuesday Microsoft released its patch for DNS as part of its regular security update cycle.

However, many found that as soon as they applied the patch, known as KB951748, they could no longer go online.

BBC News website reader Chris Rogers applied the Microsoft patch to his own and his wife's computer but discovered that afterwards neither machine could get at e-mail or the web. His anti-virus software could no longer update either.

"Basically, the [Microsoft] update had crippled both PCs," he told BBC News.

The problems only affected those with machines running Windows XP or 2000.

A spokesman for Microsoft said PC owners were not contacting it about any problems the update caused.

Mr Rogers found restoring the PC's operating systems back to before the security update was installed, restored access to the net.

He, and many others, traced the problem to a conflict with the ZoneAlarm firewall.

As news of the problems spread, CheckPoint software, which owns ZoneAlarm, issued a statement about the problems.

While it prepared a fix for the fix, Checkpoint advised users to uninstall the Microsoft security update or temporarily lower the firewall settings to "medium".

Late on 9 July CheckPoint released an update to ZoneAlarm, version 7.0.483, that solved the conflict.

Mr Rogers said installing it and re-booting his machines fixed all the problems.

He said he could understand Microsoft being reticent with details about the patch given its sensitivity.

"But," he added "it would seem reasonable for [Microsoft] to test their patch against what is probably the most popular software firewall."
[Jul 10, 2008 7:45:34 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: ZA

Once again, ZoneAlarm fail. I don't like ZoneAlarm.
[Jul 10, 2008 7:48:30 PM]   Link   Report threatening or abusive post: please login first  Go to top 
JmBoullier
Former Community Advisor
Normandy - France
Joined: Jan 26, 2007
Post Count: 3716
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: ZA

To OnePelican and others:
As usual, things go fast in WCG's fora. Your post arrived three hours after the problem is considered as closed here.
See this thread DANGER New MS Updates for details.

By the way the title of your thread is not very helpful for other members who would search this forum for related problems. Please be a little less cryptic next time. smile

To Didactylos: We knew it already. smile
Personally, as long as "once again" is once every few years as it has been for me since ten years or more I am very happy. I have used other security tools (e.g. Norton/Symantec) which are not better (to say the least) and much more expensive, and I have read here trouble reports for several others (Kaspersky, Comodo, etc...) that I am not inclined to try for myself. So I think that bashing one or the other does not help much. Let's just help to fix problems.
Regarding this story I rather have the feeling that MS has not informed all developers fairly. Fortunately ZoneAlarm has reacted faster than MS will ever do.

Edit: Fixed the link

Cheers. Jean.
----------------------------------------
Team--> Decrypthon -->Statistics/Join -->Thread
----------------------------------------
[Edit 1 times, last edit by JmBoullier at Jul 10, 2008 11:58:06 PM]
[Jul 10, 2008 11:55:11 PM]   Link   Report threatening or abusive post: please login first  Go to top 
twilyth
Master Cruncher
US
Joined: Mar 30, 2007
Post Count: 2130
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: ZA

Thanks to Jean and OP. I had been wondering about this and after the first 2 machines decided that installing the update wasn't a good idea. Guess I need to reconsider. Good to know I can reset my firewall.
----------------------------------------


[Jul 11, 2008 5:35:45 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: ZA Revisited

If ever you have an issue with ZA on board, don't look at us wink . Flaring up again, just to record a question and answer on the Berkeley forums... a DIY finding at that:
Unread Message 27964 - Posted 13 Oct 2009 13:37:21 UTC by Professor Ray

Event Type: Error
Event Source: BOINC
Event Category: None
Event ID: 1
Date: 10/13/2009
Time: 9:03:37 AM
User: N/A
Computer: HAL9000
Description:
The description for Event ID ( 1 ) in Source ( BOINC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: BOINC error: 183, Another instance of BOINC is running.


Only one instance of each: BOINCMNGR BOINCTRAY in msconfig.

No entries in [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run or

C:\Documents and Settings\All Users\Start Menu

or


C:\Documents and Settings\user_name\Start Menu\Programs\Startup

Unread Message 27983 - Posted 13 Oct 2009 19:53:37 UTC - in response to Message 27964 by Professor Ray.

O.k., I think I found the culprit here. Most likely this was a Zone Alarm issue.

I noticed in the Zone Alarm alerts log that ccEvtMngr (a Norton AV component) was trying to phone crl.verisign.net and was being blocked by ZA. According to the event log, the BOINC error 1 happened immediately after 2 consequtive ccPwdSvc events.

I put the IP address for crl.verisign.net (197.7.48.190) into the trusted zone and allowed Event Manager Service (ccEvtMgr.exe) to have trusted zone access.

After rebooting, I notice 3 consecutive ccPwdSvc events and no BOINC error.

Hmmmmpf. Whoda thunk it was a permissions issue.

----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
[Oct 14, 2009 9:31:09 AM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread