#
# Shambler config file
#  $Id: README,v 1.3 1997/01/29 07:33:59 jay Exp jay $
#   By Jay D. Allen  
#
# This file contains a list of valid usernames -or- UIDs
# When the shambler runs it will search the process table
# for any UIDs or usernames that DO NOT appear in this list.
# Any UID or username that does not appear in this list will 
# be killed, and a message logged via syslog.
#
#  How to use:
#   1. edit a ccopy of this file
#      to include root and 
#   2. invoke shambler periodicly via cron
#      shambler -c /my/path/to/shambler.config
#   3. Must be run as root
#   5. Don't even think of installing this setuid
#
#  This File:
#  1.  All lines starting with a "#,space,tab, or newline" are 
#     ignored as comments
#  2. All lines starting with an alphanumeric are assumed to
#     be a username or UID.  In either case, getpwent() is
#     consulted to find the other UID=username, and username=UID.
#     One user per line
#
#  Commandline:
#   shambler -c <configfile name> -d -k
#   -c    Required - The configfile name
#   -d    Optional - Turns on debugging
#   -k    Optional - "just kidding", does everything BUT the actuall kill
#
#  For example:
jay
root
bin
judith
nobody
peter
504
#
# The users jay,root,bin,judith, and whoever user ID "504" is
#   will be allowed to run.  Any OTHER user IDs found running 
#   will be killed.
#
# Why the shambler?
#      The original intent was to use this as part of a larger
#   security product.  Unfortunately I can't come up with more than
#   a few specialized situations that it might actually help you.
#   On the other hand, it can't hurt.  Think of the shambler as a
#   booby trap; cheap (no overhead), easy to install, simple to
#   use, and hurts like hell if anyone actually falls into it. :)
#
