I switched off banning Ezip's since a very irate customer needs them. But I still had a Bagle slip through, I have updated my rule file many times since this email. Is there something else I need to do to stop Bagle?
Thanks Timothy C. Bohen CMSInter.Net LLC / Crystal MicroSystems LLC =========================================== web : www.cmsinter.net email: [EMAIL PROTECTED] phone: 989.235.5100 x222 fax : 989.235.5151 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pete McNeil Sent: Thursday, March 18, 2004 2:42 PM To: [EMAIL PROTECTED] Subject: [sniffer] Bagle.Q rule added We have just added a rule for the Bagle.Q worm derived from data at the following link: http://www.auscert.org.au/render.html?it=3957 The rule should be present in your next update. A full rule-base compile is under way. Thanks! _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
