View Single Post
  #12  
Old February 15th 05, 08:07 PM
Gary S. Terhune
external usenet poster
 
Posts: n/a
Default Security Problems Plague XP SP2 via Symantec/McAfee

If you look at the Q&A posted by Paul, you'll see that it's rather the
opposite: They don't report their status to WSC until you apply the
update that provides for the exception of WSC form the general rule. The
general rule is to obscure its status from malicious code. I'm still at
a loss to understand how that could be a problem. What, the code is
going to see that Norton is up to date, tuck its tail between its legs
and run the other way?

--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm

"Ken Gardner" wrote in message
...
Gary S. Terhune wrote:

One result of this combination
of affairs is that while installing such apps, the new Windows

Security
Center may warn, repeatedly, that the programs are not up to date.
Symantec and McAfee consider this detrimental to the "user
experience"--and in a way, I can't blame them. It *is* disconcerting

to
get repeated warnings that you aren't protected while you are in the
very act of installing protection.


Norton solves this by deliberately disabling Windows Security Center
during installation (which makes one wonder about the architecture of
Windows Security Center, doesn't it?)


Symantec's explanation, as I remember it, seems to be that it is a
security risk for its products to report their status to windows
Security Center. But you make a good point anyway.

Ken


Ads