Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw From: CHESS@YKTVMV.BITNET (David.M.Chess) Newsgroups: comp.virus Subject: Re: IBM Virus Scanner. (PC) Message-ID: <0002.9102271603.AA00262@ubu.cert.sei.cmu.edu> Date: 22 Feb 91 16:13:58 GMT Sender: Virus Discussion List Lines: 17 Approved: krvw@sei.cmu.edu If you have a version of VIRSCAN that is labelled 1.23, what you have is a (quite old) copy of the INTERNAL USE version of the program. The internal version number and the product version number are on two entirely different tracks (we'll be fixing this soon!). So internal 1.23 is in fact *older* than product 1.2. (The next versions of both will probably be called "2.0", so this problem will go away.) The current version of the product is 1.3; it should be available in IBMLINK in the Electronic Software Distribution section (this is what I'm told; I've never used IBMLINK myself). The one source of virus signatures (suitable for use in VIRSCAN, for instance) that springs to mind is the list that is published in Virus Bulletin. That's a UK publication; I'm not sure how likely you are to find it in a US library, for instance... DC