McAfee could detect the bagle.f because I guess it had static
parameters. 

I assume Bagle.j is somewhat dynamic, so although McAfee say they can
detect is, mine hasn't, because it can only detect it once decrypted.

The page you refer to below states that only McAfee gateway products can
detect the encrypted zip (for variant w32/bagle.k). People using declude
will only be running the command line scanner, not the gateway product -
That's correct isn't it Scott?

Regards,
Lyndon.

-----Original Message-----
From: Welch, Tom [mailto:[EMAIL PROTECTED] 
Sent: 03 March 2004 16:10

McAfee says they can detect the encrytped zip files.

http://vil.nai.com/vil/content/v_101074.htm

Tom


************************************************
Email checked by UKsubnet anti-virus service
To prevent email abuse & block spam
contact [EMAIL PROTECTED]
Tel: +44(0)8712360301 Web: www.uksubnet.net
Fax: +44(0)8712360300

Powered by UKsubnet Internet Service Provider
Business to Business Internet (ISP)
************************************************


To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/

Reply via email to