Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

lsat(1) [debian man page]

LSAT(1) 						User Contributed LSAT Documentation						   LSAT(1)

NAME
lsat - a security auditing tool SYNOPSIS
lsat [OPTION] DESCRIPTION
Linux Security Auditing Tool (LSAT) is a post install security auditing tool. It is modular in design, so new features can be added quickly. It checks inetd entries and scans for unneeded RPM packages. It is being expanded to work with Linux distributions other than Red Hat, and checks for kernel versions. Output is in lsat.out. On subsequent runs, previous output is in lsat.old. OPTIONS
-d diff current and old md5 runs, output in lsatmd5.diff -m <distribution> Force a specific distribution test Names are: redhat, debian, mandrake, solaris, gentoo -h Show LSAT help -a Show LSAT advanced help -o <filename> Output filename, default is last.out -r Check rpm integrity. RedHat or Mandrake only. -s Be silent. No output at all. -x <filename> Filename is a text file consisting of modules to exclude from being run. This should be a comma, tab or newline delimited file, with just the name(s) below one wishes to exclude. Module names (with a small description) are: bpass check for bootloader passwd cfg check runlevel daemons (redhat) dotfiles check for dotfiles files check for sticky bits, etc forward check for network forwarding ftpusers check ftpusers file for bad entries inetd check for unneeded services inittab check runlevel, etc. ipv4 check for other things in ipv4 issue check issue banner kbd check kbd/login perms limits check limits file logging check for enough logging md5 perform md5 of all files on sys modules check for loadable kern mod. net check network open check open files passwd check passwd file for bad entries perms check permissions on files pkgs check for unwanted packages promisc are we in promisc mode? rc check for unwanted rc files rpm perform rpm integrity check securetty check secure tty set check for SUID files ssh check ssh config startx check for tcp listening in X umask check default umask write check world read/write files www output in html -v Be verbose about it. -w Output file is in html format. MODULES
Current modules are checkbpass, checkdotfiles, checkfiles, checkftpusers, checkhostsfiles, checkinetd, checkipv4, checkissue, checkkbd, checklimits, checkmodule, checkmd5, checknet, checknetforward, checknetp, checkopenfiles, checkpasswd, checkperms, checkpkgs, checkrc, checkrpm, checksecuretty, checkset, checkssh, checkumask, checkwrite and checkwww. A breif description is included in each module. Writing a module is fairly easy and straightforward. See README.modules for more information. LICENSE
This software is licensed under the GNU/GPL, please see http://www.gnu.org for more details. BUGS
Doesn't correct the problems that it discovers (yet). Running on Solaris is not fully functional. AUTHOR
Robert Minvielle <number9 at www dot dimlight dot org> If that fails, <triode at users dot sourceforge dot net> perl v5.10.0 2008-05-04 LSAT(1)

Check Out this Related Man Page

GRID-MAPFILE-CHECK(8)						  Globus Commands					     GRID-MAPFILE-CHECK(8)

NAME
grid-mapfile-check-consistency - Add an entry to a grid map file SYNOPSIS
grid-mapfile-check-consistency [-h] [-help] [-usage] [-version] grid-mapfile-check-consistency [-mapfile MAPFILE] | [-f MAPFILE] DESCRIPTION
The grid-mapfile-check-consistency program performs basic checks for validity of a gridmap file. These checks include checks for existence, duplication of entries, and valid local user names. If the gridmap file is valid, grid-mapfile-check-consistency exits with a zero exit code, otherwise it exits with a non-zero exit code. In either case, it displays information about its progress as it parses and validates the gridmap file. By default, grid-mapfile-check-consistency will check the gridmap file named by the GRIDMAP environment variable if present. If that variable is not set, it will check the file $HOME/.gridmap for non-root users if present. If that doesn't exist or grid-mapfile-check-consistency is run as root, it will then check /etc/grid-security/grid-mapfile. This can be changed by the use of the -mapfile or -f command-line options. The full set of command-line options to grid-mapfile-check-consistency are: -help, -h, -usage Display the command-line options to grid-mapfile-check-consistency. -version Display the version number of the grid-mapfile-check-consistency command. -mapfile MAPFILE, -f MAPFILE Check the gridmap file named by MAPFILE instead of the default. EXAMPLES
Check that the gridmap file in /etc/grid-security is valid: % grid-mapfile-check-consistency -f /etc/grid-security/grid-mapfile Checking /etc/grid-security/grid-mapfile Verifying grid mapfile existence...OK Checking for duplicate entries...OK Checking for valid user names...OK Check a gridmap file that has an invalid local user name: % grid-mapfile-check-consistency -f /etc/grid-security/grid-mapfile Checking /etc/grid-security/grid-mapfile Verifying grid mapfile existence...OK Checking for duplicate entries...OK ERROR: baduser is not a valid local username ERROR: Found 1 invalid username(s) ENVIRONMENT VARIABLES
The following environment variables affect the execution of grid-mapfile-check-consistency: GRIDMAP Path to the default gridmap to check. FILES
The following files affect the execution of grid-mapfile-check-consistency: $HOME/.gridmap Path to the default gridmap to check if the GRIDMAP environment variable is not set for non-root users. /etc/grid-security/grid-mapfile Path to the default gridmap to check if GRIDMAP environment variable is not set and the above file does not exist. SEE ALSO
grid-mapfile-add-entry(8), grid-mapfile-delete-entry(8) AUTHOR
University of Chicago Globus Toolkit 5.0.1 03/19/2010 GRID-MAPFILE-CHECK(8)
Man Page