Title: UNaXcess Version: 1.0 Submitted: Dec 1 1986 Author: decvax!cwruecmp!ncoast!allbery Submittor: decvax!cwruecmp!ncoast!allbery Description: unix bulletin board Since this submission's README did not include a description of the program, I decided to add one myself. This program is a UNIX based bulletin board system, much like the ones you find running stand-alone on micros. It allows for bulletins, and several different conferences, and file up/down load (within the bulletin board system) - Xmodem and kermit transfers are supported if you already have these programs. Priveleged users can be given access to the shell (or some other program - this is configurable). There are actually 5 normal levels of privelege available. (six if you include the "new" level). Users have passwords, and the passwords are kept encrypted - similar to the /etc/passwd format. UNaXcess can be set up as an account's login shell, so that outside users can use UNaXcess without having an account. Users with accounts can also access the board by running the "ua" main program. UNaXcess must be configured by setting aside a user-id (really an account name) for use by this system - many of the program are configured as set-uid to this account. The home directory for this account is the directory tree where all files and conferences are stored. UNaXcess comes with a script to install the system much like the "Rn" config script, but it expects to be run as root, and may muck around with the password file. I did not actually run this script (I don't currently have root privledge - and I hate running things as root unless I am sure about what they do anyway!), so I did all the things the script would have done, but by hand - it looks quite reasonable. One question in the install script confused me at first: "What is the login name of the user who can't log directly into UNaXcess?" This is the name of the account that is set aside for remote UNaXcess logins - users logging in this way will be asked for an UNaXcess account name to use. Oh, I didn't change my password file either - I made a minor change to param.c [#ifdef JPNHACK] to compile in the base directory instead of looking it up in the password file, I put all the programs into a special directory instead of /bin, I made all the setuid programs setuid to ME, and I allow access via the following shell script: