This feature should be add it

  • Thread starter Thread starter Patrick
  • Start date Start date
P

Patrick

I think it should be a good idea if microsoft integrates
tracking cokkies detetion to the scanner.
 
Yes, it is already known that this feature is not a part of MSAS, hopefully
it will be supported by beta 2.
 
Andre Da Costa said:
Yes, it is already known that this feature is not a part of MSAS,
hopefully it will be supported by beta 2.

--

Andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy
http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
Click to expand...


Of course, and since cookies are not spyware, this leads down the path
of the product becoming also a privacy tool. Delete cookies, purge
Flash cookies (.sol files), delete MRUs, purge the browser temp file
cache, wipe the browser history, purge the auto-complete and form
database, wipe the recent docs list (and the recent programs list in the
Fisher-Price XP Start Menu), and so on. You end up wasting a lot of
manpower on adding, maintaining, and improving privacy functions that
could've been spent on improving spyware detection. For example, MSAS
only *polls* for changes so you can change the hosts file and it'll be a
minute before MSAS alerts you to the change. The program that made the
change is long gone. This is similar to how WinPatrol works. Prevx
Home catches the change immediately and hangs the program until the user
authorizes it so Prevx also knows which program to let the user allow or
block in future similar events. MSAS and WinPatrol catch the change but
notification is late. They monitor instead of intercept. But changing
the code to intercept rather than monitor would be a major paradigm
shift in operational behavior.

I'd rather see Microsoft expending its manpower on improving spyware and
malware detection so, for example, it could eradicate everything that it
detects, including CoolWebsearch and eventually the rootkits, too, and
know under which environment it can eradicate that crap, like having to
reboot into Safe Mode or even Recovery Console or another .dat
bootsector replacement to do the eradication before Windows even gets
loaded. Focus on what the product is called, anti-SPYWARE (although
anti-MALWARE might be more appropriate). There are plenty of freebie
tools around, like cookie managers or browser add-ins with white- and
blacklisting, MRU cleaners, browser history cleaners, and other free
privacy tools. Make the primary purpose of the product the focus of
efforts to make it the best for that function, and maybe later waste
time trying to roll in a bunch of nice-to-have fluff functions.

Which is more important: catching (and eradicating) the spyware/malware,
or deleting cookies? If you have your suite of programmers working on
privacy functions within MSAS, you sacrifice their man-hours in
improving spyware/malware detection and eradication.
 
Vanguard said:
Which is more important: catching (and eradicating) the spyware/malware,
or deleting cookies? If you have your suite of programmers working on
privacy functions within MSAS, you sacrifice their man-hours in
improving spyware/malware detection and eradication.
Click to expand...

There is a distinction between friendly cookies and
*tracking cookies*.

And this is a function users want !
 
plun said:
There is a distinction between friendly cookies and *tracking
cookies*.

And this is a function users want !
Click to expand...


I didn't say it wasn't a feature that users want. It should be a
feature that gets lower priority than the primary function and supposed
focus of the program. Of course, Marketing always gets in the way and
often pushes for features that are often asked but which have little to
do with the what the program is supposed to do. Since MSAS will be
free, maybe Marketing will not interfere too much, yet there will be the
Enterprise or Corporate version that will generate revenue but the
demands for what features are in that product are different than the
wants of end users.
 
Back
Top