-----Original Message-----
(e-mail address removed) wrote on 2005-07- 28 :
Yes, it is a common practice and no it is not malware.
Well, It is NOT common practise
Every antivirus program from "partners" to MS signals to Security
center. And these notificatons should NOT be turned off.
But maybe some of them changed this ? I can see that if it is so
easy to change Security center notifications with malware MS
can remove it from XP or it must be better protected
But this can also be a Spybot bug !
Nevertheless its important that newbies, normal users trust
Security center and notifications.
--
plun
Check out some other newgroup besides this one sometime
and you will see the question frequently asked about how
to stop the SP2 warning messages. I manually turned off
those notifications as have a lot of other people who
choose options other than what Microsoft recommends.
Otherwise, you will be nagged to death that some
recommended options are not set. I know they are not set
because I chose an option that I control rather than go
on auto-pilot. I don't want the constant warning
messages. I choose to manually check for Windows updates
too and I do keep my machine current with updates.
Consequently, I turned off that notification and now
Spybot is nagging me about that. I will just ignore
those Spybot "Security Threat" warnings. The last thing
I need is MSAS nagging me about it too. So, please do
NOT add an MSAS agent to report this. Geez. As for the
comment about the logic of letting other applications
handle it... I chose to let McAfee security center
control virus software because Virus protection is what
they do. It's their reason for being. If Windows
security center is used to monitor virus software it will
be monitoring another vendor's software. Ar least that
is the case until such time as Microsoft rolls out its
own virus software. Then, it might make sense to have
Windows security center monitor virus software. In the
meantime, how would using Windows security center to
monitor McAfee virus software possibly make more sense
than letting McAfee monitor its own software?
-----Original Message-----
Well, common practise ?
This is a basic function within Security center to
check if antivirus program are running.
And it is not a common practise to disable
notifications about this. (Except when SP2 came out and
Symantec refused to make it compatible with Security center)
I cant see any logic to let other applications handle it.
And was this notification disabled by a user, program or malware ?
If it is malware Security center must be better protected maybe
with a new MSAS "agent".
IMHO
--
plun
CurtB wrote :
It is common practice for these notifications to be
turned off to eliminate the SP2 nag messages where they
don't apply. Now Spybot is generating a nag mesage about
the notifications that were turned off (not a desirable
option in my opinion). If a user uses McAfee's security
center, they would not want SP2 nagging them because SP2
security center is not monitoring viruses. That is the
primary function for McAfee, Norton, etc. so it is only
logical to let the Virus software handle everything
dealing with viruses.
-----Original Message-----
Hi
Did a user or was it malware turning off notifications ?
It is really easy to set this registry string with some
sort of malware......
Symantec warned about this when SP2 came out.
--
plun
-----Original Message-----
Spybot is just reporting as a security threat the fact
that the user has turned off some security center
notifications. It's not reporting found spyware.
-----Original Message-----
Hi
My Spybot detected two regestrykeys wich where modifiied.
See below.
--- Report generated: 2005-07-26 18:06 ---
Security Risks: Settings (Registry change, fixed)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security
Center\AntiVirusDisableNotify!=dword:0
Security Risks: Settings (Registry change, fixed)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security
Center\AntiVirusOverride!=dword:0
--- Spybot - Search && Destroy version: 1.3 ---
2005-04-26 Includes\Cookies.sbi
2005-07-22 Includes\Dialer.sbi
2005-07-22 Includes\Hijackers.sbi
2005-06-23 Includes\Keyloggers.sbi
2004-11-29 Includes\LSP.sbi
2005-07-22 Includes\Malware.sbi
2005-07-22 Includes\PUPS.sbi
2005-04-27 Includes\Revision.sbi
2005-07-22 Includes\Security.sbi
2005-07-19 Includes\Spybots.sbi
2005-02-17 Includes\Tracks.uti
2005-07-22 Includes\Trojans.sbi
WHY DOESNT MICROSOFT DETECT THIS IMPORTANT SECURITY
ISSUES????????????????
.
.
.
.
.