
Here's a quick "HOW TO" on using 'tiger'...

First:  Make sure you are using a 'tigerrc' file to your liking. This
        file is by default shipped with all checks enabled. You should
	probably edit it to enable only the checks you are interested
	in.

Second, for just a test run, it is *NOT* necessary to install 'tiger'.
Just 'cd' into the top-level tiger directory and run './tiger'.  This
will create a security report after some time (times vary based on system
size and extent of checking defined in 'tigerrc').

If you fix some things, and want to run just part of the system without
having to wait for the entire thing, you can run any of the scripts 
there standalone.  Just use './scripts/scriptname'.  The output will go to
stdout, so if you want to save it to a file, you'll need to redirect it.

A complete HTML report can be generated by using the '-H' option on the
tiger command line. This will generate a HTML report with hyperlinks to
the message text. If a HTML report is not desired, you can follow the
procedures below.

If you want more information on a particular message generated by 'tiger'
(or any of the scripts), you can use the 'tigexp' (TIGer EXPlain) facility.
You have three choices here.

First, if you just want more information on a specific message, just use
'./tigexp msgid', where 'msgid' is the text inside the [] associated with
each message.  For example, to obtain more information about:

--WARN-- [acc001w] Login ID backup is disabled, but still has a valid shell 
         (/bin/sh). 

one would use './tigexp acc001w'.

Second, if you want to insert the explanations in the report, you can
either run 'tiger' (or the individual scripts) with the '-E' option,
or if you have already run it, then use 'tigexp -F report-file'.  This
will write a copy of the security report to stdout, with explanations
inserted.

The third option is to generate a separate explanation file from a
report file.  To do this, use 'tigexp -f report-file'.  An explanation
report will be generated with message identifiers with each explanation.
This can be used when the report file has lots of repeated message ID's
and inserting explanations will increase the size of the report to
absurd proportions.


------------------------------------------------------------------------

Running 'tiger' regularly.

First: It still isn't necessary to "install" 'tiger'.  Installing it
is only a convenience.  If you do not install it, then it will be
necessary to either invoke 'tiger' (or the individual scripts) with
the '-B' option or 'cd' to the 'tiger' directory before running it.
The '-B' option informs the scripts where the top level 'tiger'
directory is (_B_asedir).

You have two options when running 'tiger' regularly.  The first is
to simply run 'tiger' out of cron.  Since on large systems, a full run
can take hours, this is probably not desirable.

The more desirable is to use 'tigercron'.  With 'tigercron', it is
possible to run the individual scripts spread out over a time period
(some can be run three times a day, others once a week or month).
In addition, 'tigercron' will (on some systems) e-mail a "change"
report to the specified person (in 'tigerrc').  The "change" report
will only contain "new" information and will only be mailed when
there *is* new information.

This can be helpful to make Tiger behave as a Host Intrusion Detection 
System (HIDS) but it has some caveats, make sure to read README.hids
if your intention is to use Tiger in this way.

------------------------------------------------------------------------

Installing 'tiger'.  If you do decide to install 'tiger', you can
use the provided './configure' script. This script generates modifies
the 'tiger', 'tigercron', 'config' and 'Makefile' file and sets the Tiger
directory so that they can run properly once installed. You can run
the 'configure' script with the following options (check 
'./configure --help'):

  --with-tigerhome=LOCATION       Location of all Tiger files 
                                  (default /usr/local/tiger)
  --with-tigerconfig=LOCATION     Location of Tiger configuration files
                                  (default /usr/local/tiger)
  --with-tigerwork=LOCATION       Location of all the temporary files created 
                                  by Tiger
                                  (default /usr/local/tiger/run)
  --with-tigerlog=LOCATION        Location of all the logfiles created by Tiger
                                  (default /usr/local/tiger/log)
  --with-tigerbin=LOCATION        Location of the Tiger binaries
                                  (default /usr/local/bin)

Then just type 'make install'.  

NOTE NOTE NOTE: It is important that the destination
directory (TIGERHOME) is *NOT* be the same as the source directory
(where 'tiger' was extracted).  The Makefile currently doesn't have
the smarts (I'm not sure it has any) to handle such a situation and
will mangle TIGER horribly.
------------------------------------------------------------------------

