This is the install file for LSAT. Yes, after almost
a year in existance and going all the way to version
0.6.2, we now have an install file.
Just like they tought you in CS school, eh?
Enough with the informalities, here it is.
We assume that you have not even unpacked LSAT yet...
kindof strange as this is the first set of instructions,
but nevertheless, here we go...
Dowload lsat-.tgz or .zip, depending on your
preference and place it in any good looking directory.
I prefer to put it in my home dir. You can use the built
in "install" feature to install it where you want later.
For the .tgz file:
tar -xvzf lsat-[version].tgz
For the .zip file:
If configure complains, please send me an email. If you
don't have configure, you probably need it. You could do
a manual build by reading through the make file. Being as
you are paranoid (you are using this right?) you have
probably already checked the Makefile.in just to make
sure I was not doing anything clever. :O
To install lsat in /usr/local/bin do a
To build the manpage do a
To install the manpage do a
If you are modifying or building your own modules,
you will find that
can come in really handy, so I included it for you. :)
To run lsat do a
Options: (you can get this from ./lsat -a, or a simple
help screen with ./lsat -h)
-d diff current and old md5, output in lsatmd5.diff
-f Force a specific distribution test.
Distro names are:
If no -f option, lsat will guess. If lsat can
not guess the distribution, default is redhat.
-a Show this (advanced) help page
-o Output file name -- default is lsat.out
-r Check rpm integrity -- redhat or mandrake only
-s Silent mode
-v Verbose output
-w Output file in html format
-x eXclude module(s) in filelist from checks...
modules listed in filename will be excluded
from checks. Valid module names are the module
names themselves without the check.
(e.g. set not checkset)
Any number of options can be specified on the command line.
This may take some time on older systems as it (at some point in time) does
an rpm -qa while checking installed packages. It also checks all SETUID and
SETGID files on the system. On a system more "modern" than mine it
should not take long.
The output is in the file in the directory where lsatmain was run and
should be called lsat.out. If you have previously run lsatmain then the
previous output will be moved to lsat.old. This is so that you may check
your imcremental security improvements to the system.
Ok, the documentation for LSAT is as follows: in order
of how often they are modified:
modules.html and README.modules - gives a nice descript of what each module
does and also a primier on how to build modules.
changelog - whats new, whats old.
README - basic stuffs, sometimes added to.
INSTALL - a new file, but I do not see it changing much. :)
You can reach me (sometimes) at number9 at dimlight dot org
and othertimes at triode at users dot sourceforge dot net