#
# version 3.0 Sep 25 11:21:02 PDT 1998

# This tool suite was written by and is copyrighted by Brad Powell ,Matt 
# Archibald, and Dan Farmer 1992, 1993, 1994, 1995, 1996, 1997, 1998 with input 
# from Casper Dik, and Alec Muffett..
#

# The copyright holder disclaims all responsibility or liability with
# respect to its usage or its effect upon hardware or computer
# systems, and maintains copyright as set out in the "LICENSE"
# document which accompanies distribution.

In this file:
-------------

	1) What is it?
	2) How do I run it?
	3) How can I run all utilities without interaction?


1) What Is Titan?
========================================================

Titan is a simple set of shell utilities and binary source which
can be used to 'harden' a Unix-based operating system.
More information is available in the ../docs directories that
ship with the Titan distribution.....

Primarily written for Sun-Solaris,v2.x many of the scripts and
mode hardening are valid for all Unix variants.

--------------------
Directory Structure
--------------------

  Titan,v3.0.4
   \--bin  (Main Titan scripts)
   \--Backup  (created when the Titan-Config script is run. Backups end up here)
   |----\bin\modules (directories with the seperate scripts that get run)
   |----lib  (stub programs and support programs)
   |------crypt  (currently empty;for future stuff)
   |----------logs  (log entries of what we changed, errors, warnings)
   |-------------docs 
   |		   \-------txt  (text format, rtu, license etc..)
   |		   |-------html (HTML, whitepapers etc..)
   |---src
         \---stubs (source for a few utilities requiring binary builds)
   |---src1 (things that really need to be compiled like noshell)


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

2) How Do I Run Titan?
========================================================
The typical scenario for hardening a host is to READ THE FULL DOCUMENTATION
before going any farther, then run "Titan-Config" to back up files, and
create the proper links for your OS version of the "Titan" command in the
topmost  ($TITANDIR) directory.

========================================================

A quick run would start with running Titan in Intro (Titan -i)  mode; 
then in Verify (Titan -v) mode such that you see what it
is the intended changes are; then follow this up by running selected 
scripts (or all depending on if this is a Firewall, a Server or a Desktop)
for those pieces you want to harden in Fix ( Titan -f) mode:

========================================================
Example Intro mode: Titan -i  (runs all modules in Introduction mode)
Example Intro mode: OR (run a single module) bin/modules/aliases.sh -i

This will print all the information about the various modules and what
each one does. After you figure out which modules you really can't run
and either move them aside, or write a configuration file (see Titan -c)
your ready to run Titan in Verify mode.

========================================================

Example Verify mode: Titan -v (run all modules in verify mode)
Example Verify mode: OR (run a single module) bin/modules/aliases.sh -v

All Titan modules for your architecture get run in verify (only) mode.
Titan gives output into log files and (by default) t_echo.res files
See the FAQ about turning on more verbose output.
After verifying if some fixes are already done on your system, and thus
further modifying your configuration script, you are ready to run Titan
in -Fix mode.
========================================================

Example Fix Mode: Titan -f (runs *all* modules and -makes changes-)
Example Fix Mode: OR bin/modules/aliases.sh -f   (fix only this one thing) 

./aliases.sh -f
 
 Decode not disabled. Fixing (commenting)
 Decode = decode: "|/usr/bin/uudecode"
 Decode = #decode: "|/usr/bin/uudecode"

========================================================
As the License reads "Run Titan at your own risk" as some hardening,
(ziplock.sh as an example) will make the system useable ONLY BY ROOT
users.......

E-mail bugs to "titan@trouble.org"

