Uh oh. Looks like someone (24.78.137.10) has the Bagle.c virus...
---------- Forwarded message ----------
Return-Path:
frank p
Uh oh. Looks like someone (24.78.137.10) has the Bagle.c virus...
Hmm... even more interesting that bitdefender (BDC/Linux-Console v7.0 (build 2492) under debian), updated a few minutes ago, doesn't seem to detect it. Fortunately, ClamAV (clamdscan / ClamAV version 0.60+BugFixesFromCVS-20030916) does after forcing an update. I think I'll update my clamav update cycle "just a bit." - Bob (Testing linux-based AV under procmail)
On Fri, Feb 27, 2004 at 07:50:26PM -0500, Bob George wrote:
frank p
wrote: Uh oh. Looks like someone (24.78.137.10) has the Bagle.c virus...
Hmm... even more interesting that bitdefender (BDC/Linux-Console v7.0 (build 2492) under debian), updated a few minutes ago, doesn't seem to detect it. Fortunately, ClamAV (clamdscan / ClamAV version 0.60+BugFixesFromCVS-20030916) does after forcing an update. I think I'll update my clamav update cycle "just a bit."
WPI's mail system filters out virii.
On Fri, Feb 27, 2004 at 09:31:01PM -0500, Bob George wrote:
Charles R. Anderson
wrote: [...] WPI's mail system filters out virii.
Clam found bagle in the attachments, as did f-prot.
This virus is sufficiently new that the campus mail filter didn't have the appropriate signature. I've contacted one of the people who administers it, and he's updated the signatures. No more of this virus should make it through any WPI campus mail. -- Frank Sweetser fs at wpi.edu WPI Network Engineer
participants (4)
-
Bob George
-
Charles R. Anderson
-
frank p
-
Frank Sweetser