10.21.98-SRS-INSTALL

This file describes how to install the SRS Client.  SRS is an
enhanced replacement for unix syslogd.  It provides all the 
functionality of syslogd, while at the same time it seamlessly 
encrypts and streams a copy of syslog output to a secured remote server.

INSTALLATION

For most machines and configurations, the following is all you need:

  gzip -d SRS-client.tgz
  tar xvf SRS-client.tar
  sh ./install.sh

The install script will create the required directories, and place
the unique certificates for the client in their appropriate directories.

You will need to edit your 'rc' files or equivalent to start the SRS client 
at boot.  You should also comment out syslogd so that it does not start at
boot, as syslogd and the SRS client cannot run at the same time.


CONFIGURATION 

The SRS client comes pre-compiled with specific and unique keys 
generated for each client.  Only one client can be used per machine, and
each client can only be used on one machine.


PORTABILITY

This software has been used and tested in the following environments.

	Solaris 2.3, 2.4, 2.5, 2.5.1, 2.6; Sparc
	Linux 2.0.x Slackware 2.x, 3.x, RedHat 2.1, 3.0; ix86
	BSDI 3.1, 4.0; ix86


STARTING THE SRS CLIENT

The client should be started at boot from /etc/rc or equivalent start 
up files.  It need not be given any arguments; however, an optional 
"-d" flag can be used if you with to run it in debug mode, which provides 
useful information on SRS internals.

The SRS client cannot run if syslogd is also running.  If syslogd is
not commented out of the /etc/rc or the equivalent file, then you will
need to kill syslogd manually before starting the SRS Client.  To
do this you may issue the following at the command line:

   kill -9 <pid> 
or 
   killall syslogd
   
   ./client [-d]

This package installs one program.  The SRS client will require the 
same priviledges as syslogd. It must be run by root, but it does not (and
should not) need to be SUID.

Both the SRS server and client have been carefully screened for possible
security problems, and are believed to be secure.  However, there can be
no guarantee.  If you find any problems (whether security or non-security 
related problems), please report them immediately. 


REPORTING PROBLEMS AND OTHER CONTACTS

Please report any bugs, problems, and enhancements to srs@repsec.com.


Copyright (c) 1998 RepSec, Inc. 
