As suggested, I downloaded and installed the revised version of Zone
Alarm and allowed MS to reinstall this KB. Result: Internet access
blocked again!
I have now stopped all automatic updates and will screen for this
diabolical program and delete it if it shows up again.
MS created this problem. MS should fix it.
Wrong! You didn't do your homework! ZA created this problem [PERIOD]. They
must have known about this and chose to do nothing about it a timely
manner!
http://securosis.com/2008/07/08/dan...ue-in-dns-massive-multivendor-patch-released/
....Mr. Kaminsky immediately reported the issue to major authorities,
including the United States Computer Emergency Response Team (part of the
Department of Homeland Security), and began working on a coordinated fix.
Engineers from *major technology vendors* around the world converged on the
Microsoft campus in *March* to coordinate their response. All of the
vendors began repairing their products and agreed that a synchronized
release, on a single day, would minimize the risk that malicious
individuals could figure out the vulnerability before all vendors were able
to offer secure versions of their products...
Uninstall this awful application, it's of no use. All it does is give a
warm and fuzzy feeling thinking you're secure - LOL.
For the average homeuser, the Windows Firewall in XP does a fantastic job
at its core mission and is really all you need if you have an 'real-time'
anti-virus program, [another firewall on your router or] other edge
protection like SeconfigXP and practise safe-hex.
The windows firewall deals with inbound protection and therefore does not
give you a false sense of security. Best of all, it doesn't implement lots
of nonsense like pretending that outbound traffic needs to be monitored.
Activate and utilize the Win XP built-in Firewall; Uncheck *all* Programs
and Services under the Exception tab.
Read through:
Understanding Windows Firewall.
http://www.microsoft.com/windowsxp/using/security/internet/sp2_wfintro.mspx
Using Windows Firewall.
http://www.microsoft.com/windowsxp/using/networking/security/winfirewall.mspx
PFW Criticism.
http://en.wikipedia.org/wiki/Personal_firewall#Criticisms
"Personal Firewalls" are mostly snake-oil.
http://www.samspade.org/d/firewalls.html
Why your firewall sucks.
http://tooleaky.zensoft.com/
"But I quickly realized the truth: The added protection provided by
outbound filtering is entirely illusory."
At Least This Snake Oil Is Free.
http://msinfluentials.com/blogs/jesper/archive/2007/07/19/at-least-this-snake-oil-is-free.aspx
Deconstructing Common Security Myths.
http://www.microsoft.com/technet/technetmag/issues/2006/05/SecurityMyths/default.aspx
Scroll down to:
"Myth: Host-Based Firewalls Must Filter Outbound Traffic to be Safe."
Exploring the windows Firewall.
http://www.microsoft.com/technet/technetmag/issues/2007/06/VistaFirewall/default.aspx
"Outbound protection is security theater¡Xit¡¦s a gimmick that only gives the
impression of improving your security without doing anything that actually
does improve your security."
In conjunction with WinXP SP2 Firewall use:
Seconfig XP 1.0
http://seconfig.sytes.net/
(
http://www.softpedia.com/progDownload/Seconfig-XP-Download-39707.html)
Seconfig XP is able configure Windows not to use TCP/IP as transport
protocol for NetBIOS, SMB and RPC, thus leaving TCP/UDP ports 135, 137-139
and 445 (the most exploited Windows networking weak point) closed.
