Slashdot Mirror

Has anyone bothered to do some fact/typo checking before posting this stuff?

Microsoft's offering was one of four suites which failed to detect all malware. The others were G-Data AntiVirusKit 2007 v.17.0.6353, McAfee VirusScan Enterprise 8.1i and Norman Virus Control 5.90.

See, I run McAfee VirusScan Enterprise on Desktops and Servers here without problems. The latest version in the 8.0 line is 8.0i patch 15. The Vista-compatible version is 8.5i which also works on Windows XP. There is no version 8.1i that I know of. Obviously this doesn't change the message that McAfee didn't earn the seal but I've never had problems with the VirusScan Enterprise line. To be frank, I've never encountered a single infection or uncontrolled virus problem on our network.

Plus, who honestly uses just *one* virus scanner on the perimeter of their Microsoft Server-system based network? I certainly don't. For example, Exchange 2003 server on the perimeter runs software from GFI which has three separate virus scanning engines. This coupled with application executable hash-based protection offered in BlackICE takes care of the rest of the problems at the desktop/server level. It's the price we pay for using MS software.

Has anyone bothered to do some fact/typo checking before posting this stuff?

Microsoft's offering was one of four suites which failed to detect all malware. The others were G-Data AntiVirusKit 2007 v.17.0.6353, McAfee VirusScan Enterprise 8.1i and Norman Virus Control 5.90.

See, I run McAfee VirusScan Enterprise on Desktops and Servers here without problems. The latest version in the 8.0 line is 8.0i patch 15. The Vista-compatible version is 8.5i which also works on Windows XP. There is no version 8.1i that I know of. Obviously this doesn't change the message that McAfee didn't earn the seal but I've never had problems with the VirusScan Enterprise line. To be frank, I've never encountered a single infection or uncontrolled virus problem on our network.

Plus, who honestly uses just *one* virus scanner on the perimeter of their Microsoft Server-system based network? I certainly don't. For example, Exchange 2003 server on the perimeter runs software from GFI which has three separate virus scanning engines. This coupled with application executable hash-based protection offered in BlackICE takes care of the rest of the problems at the desktop/server level. It's the price we pay for using MS software.

It's probably worth mentioning at this point that there's McAfee and there's McAfee - I was a (happy) customer of the home version until a forced "upgrade" to version 8 (I'd only tried to renew the DAT download licence). McAfee 8 is reliant on IE (as was the home version of Norton last time I looked) and doesn't work if IE is configured in a way that I'd consider remotely secure. I was also unimpressed with the way that it tried to replace MS' security centre and impose its own, claiming that I was "unprotected" without McAfee firewall (in spite of a software firewall from another manufacturer). Uninstalling it is also "interesting" including stuff in the registry referring to temp directories (ugh).

However, the non-home version I've used for years with a business hat on and haven't had a major issue with. Minor stuff sure - but compared to some of the problems our customers have with the competition no reason to switch (yet).

If anyone is still fighting with the home edition I'd recommend checking here: http://forums.mcafeehelp.com/
It's an official forum (not eidely publicised) but does tolerate people raising pertinent issues.

it's got a long way to go before it's in the same class as the *BSD's.

heh

McAfee is still using version 4.3.10 on their boards

I wonder how long it will take someone to get them too.

it would be ironic if a security company like them got hacked with something this easy

The files that get overwritten by Virex are:

//sw
/sw/lib
/sw/lib/libcrypto.0.9.6.dylib
/sw/lib/libcurl.2.0.2.dylib
/sw/lib/libcurl.2.dylib
/sw/lib/libdl.0.dylib
/sw/lib/libssl.0.9.6.dylib



Fink developers have already posted the correct way to embedding a dylib into a bundle on OS X on the McAfee forums
The viruses that McAfee attempts to prevent are really from Windows-land anyway. I have yet to run across a true native MacOSX virus. And finally, McAfee wasn't giving any credit to the Fink project. They should know better. No suprise then that Virex got bought out by a company called Network Ass.