Only one DLL needed... MSHTML.DLL
But this whole argument is a bit pointless...
An AV suite shouldnt *need* IE. But if it does, this on it's own
doesnt make it bad. I would have thought reliability and detection rate
might be important factors!
In the same way that malware might hijack libraries such as
MSHTML.DLL, they might also go for any other library.
Every AV system runs on an operating system. The OS makes
libraries of functions available to running programs. Potentially
any of these can be hijacked.
Can you name me a Windows AV package that doesnt use
the registry? Or the file system? Any part of the windows
can be corrupted.
Similar arguments apply to Linux and all other OS's.
So the argument that using an AV suite that needs IE
is less secure doesnt hold. However, I would say it is very short-
sighted, if a package DOES require the full IE application (as
opposed to just the dor Windows MSHTML library) for the
obvious reason that some people may have removed it.
If the AV suite simply needs some core libraries including
MSHTML.dll, these should still be available. If the user
has removed these, then he/she is a fool! These library DLLs
are used by far more applications than just ie... eg. the Help
system, MSDN Libraries etc....
Phew!
So I'm not sure whose side I'm on now, so I'll hedge my bets and
say you are all wrong!
Chris