Hi Plun,
I shouldn't have stated that Windows OneCare is State-of-the-Art, since it's
really still a Beta at this moment. However, the current real situation for
much of the OneCare target market is severely out of date or nonexistent
antimalware and OS updates, at least until a major malware infestation
occurs. Then everything gets updated or installed in a flurry, and ignored
until the next malware infestation.
The Windows OneCare Team responded to the firewall issue in their blog here:
http://spaces.msn.com/windowsonecare/blog/cns!C29701F38A601141!598.entry
The key issue isn't the firewall itself, rather its the Digital Signing and
Java. Ben Edelman's blog article exposes issues with VeriSign's handling of
certificate registration that need to be addressed regardless of the
certificate type. The CNET News.com article would concern me more had it come
from an independant source, rather than the security management arm of
McAfee. Allowing Digitally Signed ActiveX to pass through, since it is easily
identified, associated to a specific organization and blocked if necessary,
seems less risky than requiring the average user to decide.
The fact is that OneCare has the existing malware protection industry
running scared, which is a good thing for all of us. OneCare has defined what
a basic protection suite should really look like (AV, AS , FW), with the
'extras' simply invocations of existing Windows provided tools or functions
in most cases. This is the least bloated combination product I've ever seen,
with many previous users of major competing products echoing this sentiment.
Sure, a techie could put together a leaner set of products, but it would
require a techie to operate it, which is the primary problem with existing
products. But the best part is it's causing the antimalware industry to
respond in kind, with products for a broader range of customers, per the
following article and I'm sure many others.
http://news.zdnet.com/2100-1009_22-6034127.html?tag=zdfd.newsfeed
Bitman