Following files will be installed:

bbs		the user-program (clients)
bbs-guest	a startscript for starting bbs as user "guest" from login
bbsd		the daemon
bbs.conf	configuration-file for bbs and bbsd
etc/users	users-datafile
etc/kermrc	configuration for kermit (called by 'kermit -y ...')
help/*		helpfiles for bbs
scratch		an empty directory (for sockets, created and removed by 'bbs')

'bbs' creates (and removes) at runtime:
scratch/talk-*-*  sockets for 'talk'

'bbsd' creates at runtime:
etc/bbsdpid	contains pid of bbsd
etc/bbs-socket	socket to connect daemon and clients
etc/bbslog	logfile (there are also messages to console and syslog)

You want 'sz', 'rz' and 'kermit' to install 'bbs'.

1. Read README
2. Run Configure
3. Check Makefile, local.h, bbs.conf and users
4. Run make
5. Run (as root) make install. Maybe set 'bbs' suid (for 'talk').
6. Create uploaddirs according to 'users' (must be writeable for bbs-owner)
6. Make an entry in /etc/passwd for 'bbs' and/or 'bbs-guest'
7. Check permittions and locations, be sure no bbs-user can read/write
   non-public files, especially 'users', 'bbs.conf', 'bbs.log'.
8. Edit 'users'.
9. Edit 'kermrc'.
10. Run 'bbs' and assign passwords, especially for sysop.


One example for a secure setup:

Install-Directory: /users/ftp/bbs
Chroot-Directory: /users/ftp/pub
Client-Owner: bbs
Client-Group: guest
Daemon-Owner: bbsd
Daemon-Group: guest
Running daemon suid bbsd (y for yes, n for no) [y] y

Each time 'bbs' connects to 'bbsd', it sends a keyword to it in order to
authorize. This key is build from two parts, both are defined in 'local.h',
which is build by 'Configure'. One part may be overwritten in 'bbs.conf'
('Authkey'), the other is fix. If authentication fails, you get the message
wrong authorisation
connection to daemon failed
This may happen by accident e.g. if you run 'Configure' and compile a new
client but use an old daemon, so the fix part mismatches.
Be sure to install 'bbs', 'bbsd' and 'bbs.conf' unreadable for unsecure
users.

Sysop can change everyones password. On first time, log in as sysop
(with the username asked by 'Configure') and change it. A user with
securitylevel = 0 may not change his password.

For 'talk', both parties must be able to send/receive signals (SIGUSR1 and
SIGUSR2). On most UNIX this means equal real uid or equal effective/saved
uid. Look at man-page for 'kill(2)' and install 'bbs' according to. You may
run every 'bbs' at the same uid by setting a suid, this is safe, because
it has an own accounting mechanism.

