ftp.wwiv.com/ftp.wwiv.com.zip/ftp.wwiv.com/pub/BBS/THDPRO_1.ZIP/THDPRO.DOC

Text File | 1992-08-21 | 19KB | 315 lines

                              THD ProScan V.1

          First... Thank you for downloading this file.

          Credits...
     Thanks to all the sysops who, at various stages, helped in the
betatesting of this product. Many helped me to find "minor" inconsistencies
and fix them before you got to see it.
     A VERY special thanks to "Witch Doctor" for his great assistance in
betatesting the first releases and making valuable suggestions about the
program.. Many of which were implemented, And of course some which were
not.. But all of his suggestions and comments were considered.
     Witch Doctor is the sysop of...
                        THE RECTIFIED SHIPYARD
                            [phone]
                       TORONTO, ONTARIO, CANADA
     A special thanks as well to "Eternal Darkness" for his contribution of
the "user side ansi screen". He willingly gave me a number of "ansi" drawings
with permission to modify them as was necessary to suit my purpose. The ansi
your users see is only very slightly modified from the ansi I received and I
think he did an excellent job.

     THD ProScan is an upload tester for ANY BBS which is capable of sending
a command line of the following format.

"C:\UTILS\THDPRO.EXE D:\NEWFILES\TEST.ZIP"

{Where "C:\UTILS\THDPRO.EXE" is the full path and filename to the THD ProScan
executable file and "D:\NEWFILES\TEST.ZIP" is the full path and filename to
the file to be tested}.

Features..
     - Strips comments from all archives before any processing is done
        (to avoid "ansi bombs" in comments). This features will not protect
        users if the "internal" archives contain such bombs.
     - Recreates full directory structure "from" the temporary directory,
         thus allowing all internal archives to be tested regardless
         of how deeply imbedded they may be.
     - Does not allow the "overwrite" option on any of the archive types.
        (stops some forms of "hacking")
     - Add your loaders and/or archive comment to the main archive.
     - Will use one of as many as three drives to test files by
        searching in order to find enough available space on one of them.
     - "Intelligent" installation which will attempt to do as much of
        the installation for you as is possible.
     - Full control over the options available and paths to archive utilities.
     - Support for ZIP-GIF-TD0-ARC-ARJ-PAK-HYP-LZH file types.
     - Will Virus scan all filetypes regardless of types configured.
     - Remove unwanted files from the archives tested.
     - Option to hang up on users who upload viruses.
     - Option to reboot after a viral detection.
     - No Known ways to "alter" the operation of your BBS through it's use.
     - All operations controlled by a single executable file.
     - The executable file can be compressed by PKLITE (or similar utility)
        after the installation has been run, with no ill effects on it's
        proper operation.(Configuration cannot be performed on a "compressed
        executable file")

     WHAT WILL IT DO..
          THD ProScan will ..
         1) Strip the file comment and add your comment.
         2) CRC test the file
         3) FIND a drive with enough space to test the file
         4) Create a directory called "THDTEMP.$$$" on that drive
         5) Remove files (if configured) from the archive.
         6) Expand the archive into that directory while recreating
               its internal path structure.
         7) It will then scan each of the files in that directory and
               all subdirectories below it.
         8) It then selectively searches each of the subdirectories created
               for testable archives. If found, it repeats the above process
               until no more archives are found. In this way EVERY imbedded
               archive is tested, regardless of where it is in the directory
               structure or how far imbedded it is. Every directory created
               by the original archive or any of the embedded archives is
               tested and scanned by THD ProScan.
         9) Add your loaders to the archive
        10) It maintains a log in your BBS directory of all actions performed.
        11) It then proceeds to remove the temporary directory structure.
        12) Reports the appropriate errorlevel to dos.

     The actual process is of course much more complex.. But the above
overview is a decent summary.

     Requirements...
          This tester requires
          PC/XT (or compatible)
          MS-DOS 3.3 (or higher)(other "DOS" systems MAY be acceptable)
          A FOSSIL DRIVER (user output will not be sent if no fossil is found
                           but the testing will still be done)
          APPROX 325k FREE memory
                (memory requirements will vary depending on your version
                of SCAN.EXE. The actual overhead of this program is 80k)
          McAFEE's VIRUSCAN (the newer the better)
          The USER must support ANSI.

     The following utils are required depending on which file types you wish
to test.
          LHA.EXE        for "LZH" files
          ARJ.EXE        for "ARJ" files
          PKZIP/PKUNZIP  for "ZIP" files
          PKARC/PKXARC   for "ARC" files
          PAK.EXE        for "PAK" files
          HYPER.EXE      for "HYP" files
          TDCHECK.EXE    for "TD0" files
          GIFTEST(ver 4) for "GIF" files

INSTALLATION...

     Included are 4 files.. THDDEMO.COM,THDPRO.DOC,THDPRO.EXE and
THDINSTL.EXE. THDPRO.EXE is the actual upload tester and controls or
performs all actions of the "testing" from "File Allocation Table move"
to removal of the temporary directory.
     THDINSTL.EXE is the INSTALL/CONFIGURATION utility. It MUST be run
in order for the scanner to operate correctly.
     Basically all that is required is that the THDPRO.EXE be in your
current directory when you run THDINSTL.EXE.
     THDINSTL.EXE will search the executable file for any previously
configured settings. If none are found it will go through the
installation step by step. If however it finds that the installation
has previously been run, it will simply load the previous information
and take you to the final two option screens. From these two screens
you may select (by letter) to modify any of the previous configuration
parameters.
     The "original" installation process can be defaulted to by running
"THDINSTL.EXE /F". This will cause the install to NOT look for old
settings and simply start an install as if it were the first time.
     When you run the installation, it will ask you a number of yes/no
questions and depending on your answers will prompt you for certain
things. Certain things are mandatory.
        The use of "∙" (alt 249) is forbidden in ALL entries in
        the installation. If used, the string in which it was used will
        be "CUT" down to the character immediately preceding it. This
        will result in unpredictable results. DO NOT use that character.
"BBS NAME"...  This of course could be your name or alias if you prefer,
                BUT something must be entered.
               This entry MUST be between 4 and 35 characters in length.
"COMPORT"...   This MUST be a valid comport as the tester will output to
                the comport on every run. (the comport need not be active
                to run the scanner, but must exist)
"BBS Directory" This directory need not be your BBS directory. It can be
                any existing directory where you would like to keep the
                "log" file created by the tester. This is also the
                directory you will be in at the completion of a successful
                test.
"SAVED Directory"
               This is the directory into which you wish files which fail
               the scan portion or cannot be tested should be "moved".
All entries which require a "directory" require that there be no ending "\"
at the end of the path. All Filename entries require full path and filenames.
     The entries made in the installation MUST NOT exceed 40 characters
per entry. If you enter more than 40 characters the entry will be accepted,
but cut down to the first 40 characters. However If file paths are cut by
this process, the results are totally unpredictable. If any of your entries
wraps on the final two screens of the install.. THEY WILL NOT FUNCTION as
intended and you will need to use files in a different location than those
entered.
     Although the program could possibly accept filenames without paths in
some instances, I STRONGLY suggest you not accept such entries and modify
them to include a full path.

The install will attempt to locate the "SCAN and ARCHIVE" files that you
     wish to use for testing. As well as the correct number of drives that
     are available (of which THD ProScan can use a maximum of 3).
If you read the instructions given for each step during the install process
     and follow them exactly, you should encounter no problems at all with
     the setup procedure. The install can be exited at any time by pressing
     "CTRL-BREAK". No information from that session will be saved. (Unless
     perhaps you manage to press it while the program is in the middle of
     saving the information you have entered)

                              THDPRO.DOC
                          -You're reading it

                              THDDEMO.COM
     A simple demonstration of the user side view of what happens while the
scanner is running. This is included just in case you have never seen this
tester in action before. Your side will display the various utilities
performing their duties and a short explanation of what the tester is doing.

                              "THE TESTER"

     This is my first ever "real" program. It was made to satisfy a number
of people who saw my "batch program", THDscan, but were unwilling to use it
based on it's dependency on 4DOS or NDOS.
     The reason that this program uses 80k of memory is due to a very large
"stack" segment which is reserved for the use of "imbedded" archives. By
reserving such a large stack, the program is able to run recursively for
much longer and thus test imbedded archives far beyond the first level.
I may reconsider the "size" of the reserved portion in later versions. But I
trust that most "shells" from BBS programs can leave enough memory for this
program to run as is.
     This program is just as secure as THDscan and more secure than Ziplab or
PKINSERT. There is no way to change the "way" this scanner operates (without
hacking it) for a good reason. Even some of the most noted upload testers
make a very serious flaw in the way they handle uploaded archives. By not
allowing the user to change these settings, I avoid someone opening one of
those "all too evasive" back doors and hacking into your system. So please
don't ask me to change the parameters that this program uses. They are that
way for a reason. (I will of course be happy to change any that prove to be
incorrect or cause "real" problems).
     This scanner will exit with one of 4 DOS errorlevels.
ERRORLEVEL 0 - All tests were passed satisfactorily.
               - The scanner will also exit with this errorlevel under
               a number of "odd" circumstances which will avoid having
               a file fail due to some unforeseen difficulty.(This includes
               failing to supply a proper path to the file to be tested and
               a number of other small things)
ERRORLEVEL 1 - An imbedded archive failed the CRC test.
ERRORLEVEL 10- A virus was detected during the "scan".
ERRORLEVEL 15- The main archive failed the CRC test.

     The reason for having an errorlevel 1 exit, is that this tester
recognizes imbedded archives by name, And as such "could" attempt to
unarchive a file with the same extension as a valid archive format without
that file actually being an archive. This of course would cause the file
to fail the CRC test. By setting the "errorlevel for success" in your BBS
program to "1" you could avoid failing these files. However, I suggest that
the errorlevel be set to "0" as no reputable programmer would use the
extensions of known archivers to name files of another format. But it is,
of course, your option.

        The operation of the scanner could not be simpler. You need simply
run THDPRO.EXE while supplying it with the FULL path and filename of the
file to be tested. I STRONGLY suggest that you also supply the full path
and filename to THDPRO.EXE as well (not necessary but it too can help to
reduce hacking). So the proper syntax would be as follows...

        C:\UTILS\THDPRO.EXE D:\NEWUPS\TESTFILE.ZIP
        {Where THDPRO is located in "C:\UTILS" and the file to be tested
        is "TESTFILE.ZIP" which is located in "D:\NEWUPS"}

        The tester itself accepts no other parameters for operation. And
requires no further input from that point. If run without parameters , It
will simply display the correct syntax. ERRORLEVEL 0 will be returned in
any event where a file is not tested (to avoid the BBS software deleting
files due to improper syntax).
        While geared toward the testing of archived files, The tester will
viruscan any file type for which it is not configured. So having your BBS
use this tester to scan "EXE" and "COM" files is  an excellent idea. The
passing or failing of such files will be based solely on the result of
the scan and no other operations will be attempted on the file aside from
the scan. Any valid filename can be passed if you wish it to be "scanned".
I suggest that you configure your BBS to "test" all files with "executable"
extensions as well as any "OVL/OVR" files.


NOTES-
     Future Considerations include "date limiting", Protection for archives
which have been archived with "Authenticity Verification", Support for a
NON-ansi compatible user view, and  INTERNAL identification for archives.
     If a file fails the scan portion or is for some reason unable to
be tested, the file will be moved to a directory you specify. Priority
is given to a "file Allocation Table" move. Thus if the destination drive
is the same as the source drive, only the "FAT" will be modified (this
allows a 4 megabyte file to be moved in less than 1 second.) If the source
and destination differ then the file will be moved by "copying" it to the
destination and deleting the original (if the copy was successful). If the
file cannot be moved for whatever reason, it will be renamed with an
extension of "THD" (if it could not be tested) or "VIR" if it failed the
viruscan, it will be renamed during the move if it was virus infected
regardless of success of the move operation).
     This programs creates and removes a directory called "THDTEMP.$$$".
If this directory exists on any of your drives... Either rename the directory
or do not allow that drive to be used for testing. There is no recovering
from the removal of this directory.
     This program depends on the fossil driver to send messages to the user.
If no fossil is active, the testing process will still occur, but the user
side will be blank. The fossil is also used to drop carrier and/or reboot
the system if you have chosen those options in the installation.
     This program requires the user to have "ANSI.SYS" or a comparable ANSI
interpreter. If the user does not have this, he/she will see the "raw" ansi
code sent by the tester. (A non ansi dependant version is foreseen in the
not too distant future).
     I strongly suggest that after the installation is complete and the
executable file is in it's permanent place, that you make it a read-only
file. This will be yet another deterrent for "wanna-be" hackers who would
attempt to overwrite this file.
     The only known problem with this tester is that if an unscrupulous
person attempts to overwrite certain files on your system, the program will
hang pending "user input". IF YOU EVER see such a prompt on your system
while this program is running, DO NOT ALLOW the overwrite. This program
accounts for all "normal" circumstances of overwrite attempts and will hang
only if the user finds a way to overwrite files outside of this testers
control. Allowing such overwrites could result in total disaster.
        This program and all of its associated names,files,logos and makeup
are Copyright 1992 PainSoft. No duplication in whole or in part is allowed.
With the exception of duplication of the entire archived set of files for
distribution to those in need of it's services. None of the copyrighted
material may be changed in any way except by the author. Changes made by
the "original/unmodified" installation program will be considered to have
been made by the author for the purpose of this copyright. The files may be
rearchived in ANY fashion which requires them to be restored to their
original condition before use.(Portions Copyright Borland International)
        The  executable files may be  "compressed"  to save space but
        may not be distributed in this "compressed format". The Author
        accepts no responsibility  for the actions of this program. It
        is  FREEWARE  and NO charge may be made for it's distribution.
        It is NOT a commercial product and as such the ONLY acceptable
        charge for it will be  "actual, physical cost of duplication".
        I do not profit  from it  monetarily  and any attempt of other
        persons  to do  so shall be  considered an  infringement of my
        copyright.
        Other products  mentioned are  copyrighted by their respective
        owners and  include their own restrictions for use.  Please be
        sure to  register those products if requested by the copyright
        owners.

Thank You for taking the time to read this document. I hope this
upload tester serves you well and helps to keep your system free
of viral infection and a little safer from potential hackers.
                ... Pain ...
                     of
                ..PainSoft..