Re: probable virus

From: Brett Glass (brett@lariat.org)
Date: 10/31/01


Date: Tue, 30 Oct 2001 18:50:28 -0700
To: Mike Tancsa <mike@sentex.net>, freebsd-security@FreeBSD.ORG
From: Brett Glass <brett@lariat.org>

If you're running McAfee on Windows, best to go with the SuperDAT.
It's at

http://www.nai.com/naicommon/download/dats/superdat.asp

--Brett

At 10:41 AM 10/30/2001, Mike Tancsa wrote:
  

>Just to followup, the daily dat file seems to be working fine. Anyone out there using it on a regular basis, I would be interested in hearing your experiences.
>
> ---Mike

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message



Relevant Pages

  • OT: My Blank Posts
    ... In a nutshell: stoopid human error. ... want to followup to, I mark it for followup and my newsreader ... about with Windows (I run OSX and run Windows under Parallels ... Once I am done cursing Windows;-) and have rebooted I ...
    (rec.equestrian)
  • Re: Killfilters in Thunderbird
    ... any article that is a followup to that article. ... How do I do this in Thunderbird? ... free software that will do this for Windows. ... That's what I'm after too - proper filtering on Windows ...
    (uk.comp.sys.mac)
  • Re: Word 97 in XP?
    ... Word 97 will run under Windows XP Home ... Please post any further questions or followup to the newsgroups for the ... "newsgirl" wrote in message ...
    (microsoft.public.word.newusers)
  • Re: Norton internet security 2003 and windows 95
    ... [This followup was posted to comp.security.firewalls and a copy was sent ... In article, dannywork5 ... > runs windows 95b and I would like to know if this will handle Norton ... If there is a no_junk in my address, please REMOVE it before replying! ...
    (comp.security.firewalls)
  • Re: Office 2003/Word
    ... I have them here, but I think that they maybe installed as part of Windows, ... Please post any further questions or followup to the newsgroups for the ... Doug Robbins - Word MVP ... "Dale" wrote in message ...
    (microsoft.public.word.printingfonts)