home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Lion Share
/
lionsharecd.iso
/
bbs_oth
/
vkill200.zip
/
VKILL.DOC
< prev
Wrap
Text File
|
1992-06-25
|
9KB
|
205 lines
┌───────────────────────────────────────┐
████│ V K i l l │▓███
│ Version 2.0a │
████│ Release Date 06/25/92 │▓███
└───────────────────────────────────────┘
(C) 1991, 1992 Cairo Research Labs
ALL RIGHTS RESERVED
─────────────────────────────────────────────────────────────────────────────
■ INTRODUCTION ■
─────────────────────────────────────────────────────────────────────────────
VKill is an automated Virus/Archive scanner designed for use with Scott
Dudley's Maximus CBCS. It's features include:
* Capability of handling an unlimited amount of nested archives
* Fully configureable to facilitate archiver/scanner updates
* Test archives and/or contents of archives against a date stamp
to provide a method of preventing users from getting credit by
by uploading out-of-date or old archives.
* Will not accept archives other than the types you specify!
* Special Extension handling (i.e. GIF, PCX, MOD, VOC, etc).
* Eye-pleasing graphics for your users to view as VKill works!
─────────────────────────────────────────────────────────────────────────────
■ WORD FROM THE AUTHOR ■
─────────────────────────────────────────────────────────────────────────────
Computer virus infections are on the rise. We'd be kidding ourselves if we
stated otherwise. I was one of those folks who held the high opinion that
it would never happen to me. It did. Living through those several hours of
data recovery did quite a few wonders on my opinions of viruses. VKill was
written as a Maximus CBCS plug-in to offer another preventive step for us
Sysops. No one wants to see a horde of angry users pounding at your door,
because they nabbed an infected file off of your system! ;-)
Please folks, keep in mind that I am a programmer, not an author! These
docs really suck the "cosmic muffin", but they are getting better. I do not
claim in any way that VKill will work for you! The only thing I can claim is
that it works flawlessly on my system. Due to the fact that VKill is
FreeWare, and I am not charging for it's use, then I cannot promise to what
degree tech support will be given. I can be found in the MUFFIN echo for you
fido dogs, and am also active now in IntlNet and SBNet. I will be more than
happy to answer any netmails or echomail directed to me referencing VKill.
Or, if you wish, you may call my system direct:
Cairo Research Labs
Under the Nile!
(706) 596-8126 9600v.32
1:3613/12@fidonet
─────────────────────────────────────────────────────────────────────────────
■ OPERATION NOTES ■
─────────────────────────────────────────────────────────────────────────────
Operating VKill is a cinch. When a user completes an upload session, Maximus
will call a batch file called VIRCHECK.BAT. Simply place VKill in this batch
file and let her go. A sample VIRCHECK.BAT file should be included with this
archive.
VKill processes the uploaded file based upon the extension of the file. All
you have to do is ensure that the popular archivers are available in your
path, (i.e. PKZIP, LHARC, ARJ, PAK, etc). It will handle multiple nested
archives of DIFFERENT types as well!
VKill will exit on the following errorlevels:
1 - Infected File was uploaded
2 - Bad Archive was uploaded
3 - Invalid Command line parameters
4 - General error - Invalid dir, etc.
5 - Archive(files) older than check date stamp
6 - Special File Extension encountered
99 - Suspicious File Extension
If VKill detects an infected file, a bad archive, or a suspicious file
extension, the file is moved to a holding directory, and will remain there
until you delete it. This ensures that infected files and the like will not
remain online for your users!
***NOTE*** A Suspicious file extension is one that ends something that has
not been defined in your configuration file. (i.e. not a valid archive or a
special extension type).
A sample DORINFO1.DEF file has been included to allow you to test in local
mode operation.
─────────────────────────────────────────────────────────────────────────────
■ CONFIGURATION ■
─────────────────────────────────────────────────────────────────────────────
The configuration file is where everything comes together.
PATH1, PATH2 = These options simply specify which two directories to use in
case VKill encounters an archive within an archive. VKill
will essentially use these two directories to "bounce" back
and forth until there are no more remaining multiple archives.
BADPATH = This is the path of your holding directory for infected files, bad
archives, or files with suspicious extensions.
LOGPATH = This is the FULL PATH and FILENAME of the logfile generated and
maintained by VKill. It is possible to run VKill on multinode
systems, by specifying a different configuration file per node.
If you are running a multinode BBS, just make each logfile unique.
DATECHECK = This option will allow you to provide a check for old or
out-of-date archives. There are two methods of configuring the
datecheck system. See the sample config file for more info.
ARCDEF = Signifies an ARChiver DEFinition. See the config file for more info
on defining archivers.
SCANDEF = Signifies the Virus Scanner Definition. See the config file for
more info on defining your scanner.
The remainder of the config file is pretty much self-explanatory.
─────────────────────────────────────────────────────────────────────────────
■ COMMAND LINE ■
─────────────────────────────────────────────────────────────────────────────
VKill accepts the following parameters, in THIS order:
[UPLOAD PATH] - Path to uploaded file
[FILENAME] - Name of uploaded file
[EXTENSION] - Extension of uploaded file
[DORINFO] - Path of DORINFOx.DEF file....
[CONFIG] - Path and filename of configuration file
When called from a VIRCHECK.BAT, it should look something like:
VKILL.EXE %1 %2 %3 c:\max c:\max\vkill.cfg
since Maximus will pass the first 3 to VIRCHECK.BAT automatically. Actually,
Maximus will also pass as a fourth parameter the path to the MISC directory.
Since VKill doesn't use it in any way, there's no since in passing it.
A sample DORINFO1.DEF file has been included to allow you to test in local
mode operation.
In order for VKILL to obtain the information he needs on the current user's
baud rate, your COM port settings, etc, you must create a DORINFOx.DEF file
prior to calling VKill.
Here at Under the Nile, in my MENUS.CTL, under the FILE menu, I use:
NoDsp Display_File Misc\uploads Disgrace "Upload (send)"
Upload Disgrace "Upload (send)"
In my C:\MAX\MISC directory, I have a MECCA file called UPLOADS.BBS, which
looks like this:
-------------[ cut here ]---------------
[cls]
[LIghtred]Upload Policy!
[Cyan]
Please do not upload GIFS, games, or any other file not pertaining to the
format of this BBS! The file should fall into one of the following
categories:
[yellow]Programming -[white] C, BASIC, Pascal, Assembler, etc.
[yellow]Video -[white] Graphics (NO GIFS), Animation files, CAD, etc.
[yellow]Audio -[white] SoundBlaster, AdLib, .MOD, .VOC, .SND, etc.
[yellow]Multitasking -[white] Windows Applications, Desqview, Desqview/X, etc
[yellow]General Util -[white] Archivers, System Utilities, etc.
[lightgreen]
[enter]
[link]c:\max\misc\dorinfo
-------------[ cut here ]---------------
This will create a DORINFO1.DEF file for the current user. See the Max docs
for more info on this one.
─────────────────────────────────────────────────────────────────────────────
■ REGISTRATION ■
─────────────────────────────────────────────────────────────────────────────
Currently, there is no registration fee for using VKill. We have quite a bit
in store for VKill in the future, so that may change.
For the latest version of VKill, or for tech support by BBS, call:
Under The Nile! BackWoods BBS
(706) 596-8126 9600 v.32 (706) 561-6106 9600 USR DS
1:3613/12@fidonet 1:3613/10@fidonet
Magic Name VKILL will get you the latest version!
Coming soon to VKill!
─────────────────────
o Archive conversion?!
o GIF Integrity Testing!
o Remove BBS Advertisements!
o Replace Archive Comments!
o Much more!!