The Bastille Hardening Program currently has rudimentary, though somewhat
cleverly implemented, automation.  As the program runs, it maintains several
logs in /root, including /root/Bastille-input-log.  This log is an exact
duplicate of all input from the run.

If one were to copy this file to a floppy under the filename INPUT, one
could use this file as input to a run of the script on another machine, like
so:

               cd run-Bastille
	       ./Bastille1.pl < INPUT
	       
You could create 500 identical lab machines through this method. [1]

In a future release, Sweth C.'s and jjb's automation design will be
realized, allowing for a scheme that will be more forgiving of errors in the
configuration file.  Said scheme will implement key-value pairs with sanity
checks.


[1] There is a danger here: you must keep careful tabs on the INPUT file, as 
    it may include passwords, inputted in response to questions.






[1]  Under the current implementation, this does pose some danger that can be 
     avoided.  This file must be safely guarded, as it may contain
     passwords, based on options you choose.