Re: FIX for ZoneAlarm & KB951748 issue released
"Kerry Brown" wrote:
> "Stinger" <Stinger@discussions.microsoft.com> wrote in message
> news:88C199ED-4893-4EB2-81F3-1053114DB96A@microsoft.com...
> >
> >
> > "Root Kit" wrote:
> >
> >>
> >> BTW, what you provided here lacks any technical arguments which makes
> >> you sound more like a salesman than anything else. So what security
> >> software company do you represent?
> >>
> >
> > The same "software company" that includes common sense as part mission
> > statement Root Kit. Try reading the entire thread before you jump in
> > taking
> > things out of context. It's boring when people do that.
> >
> > Read back through the entire post before challenging my quotes from
> > others.
> >
> > Here's EXACTLY what Kerry said earlier word for word...
> > "There is no debating the fact that this flaw in the DNS system needed to
> > be
> > patched and it needed to be patched immediately. This has nothing to do
> > with
> > Windows."
> >
> > Nothing to do with Windows??????????
>
> I stand by the statement. The flaw iself had nothing to do with Windows. It
> was a flaw in the DNS communications protocol. Windows was using the
> existing protocol which was flawed. This meant that Windows had to be
> changed to work with the new protocol or it would be vulnerable. How is this
> a Windows problem? It's a DNS problem that all developers that make products
> that communicate with DNS servers have had to deal with.
>
> I agree with Root Kit. You havn't provided technical details of how a
> software firewall that does outbound monitoring improves security over the
> Windows firewall. You haven't tried to refute the fact that Zone Alarm's
> monitoring of and reaction to system file changes is flawed. You obviously
> misunderstand what caused Microsoft to update the DNS client in Windows. I'm
> done with the conversation unless you can provide us with some technical
> reasons that back up your assertions. I like a good debate as much as
> anybody but it's pointless unless you at least try to back up your
> statements.
>
> --
> Kerry Brown
> Microsoft MVP - Windows Desktop Experience: Systems Administration
> http://www.vistahelp.ca/phpBB2/
> http://vistahelpca.blogspot.com/
>
>
>
>
And I've yet to see anyone answer the most important question, you include
Kerry..
"Why was the patch even produced by MS if there wasn't a "problem" with the
OS?"
Windows has to be changed to work with the new protocol? So either there
was something wrong with Windows before or after the new protocol was
invoked...which is it? Can't have it both ways. If everything was fine
before the new DNS protocol was invoked, we're right back to my question
above. You don't need to have technical expertise to see when people dance
cokmpletely around a subject folks.