Demonstrates how one might write a program that creates VDL models from generic scan codes. This program has been compiled and tested on Microsoft Windows NT 4.0.
ANSI C version of the previous example.
This Python program demonstrates how one might write a program that uses VFind Turbo to scan web site accesses.
Runs VFind alone on a Sun Solaris 2.X system. Output is mailed to root.
Runs VFind with UAD on a Sun Solaris 2.X system. Output is mailed to root.
Runs VFind with CIT, UAD, Loop back Head and Loop back Tail on a Sun Solaris 2.X system. This is the recommended script for full production runs. Output is mailed to root.
Uses VSTK to scan a multi-file tape for hostile content. For example: if you had a tape that contained more than one tar file, this script would continue scanning until it reached the end of information marker rather than the end of file marker at the end of each tar file.
Uses Bhead and VFind to scan the first few bytes of a disk.
Runs CIT by itself.
Runs THD by itself.
Runs UAD and VFind together using SmartScan.
Same as above but adds the loopback tools.
Runs CIT, UAD, and VFind.
Runs CIT, UAD, VFind, and the loopback tools.
Use wget, UAD, and VFind to download, scan, and save only infected files.
Determines your VTN (VFind Throughput Number) and can be used to speed up VFind on your system. WARNING: This script has only been tested on Sun Microsystems Sparc Solaris 2.6. Read the program comments prior to operation.
Makes it easier for users to run UAD for identifying and decomposing complex files.
Isolates infected files by setting their permission bits to zero. WARNING: If the script changes permissions on system critical files, the system can become unstable.
Automatically moves infected files to a quarantine directory.
WARNING: moving system critical files can cause the system to become unstable.
Interactively deletes infected files.
WARNING: Deletion of system critical files can cause the system to become unstable.
This script scans the file system by examining the contents of the /etc/exports table. We are not sure why one would want to do this, but it is a great example of how easily the VSTK can be customized for your specific needs.