home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Usenet 1994 October
/
usenetsourcesnewsgroupsinfomagicoctober1994disk2.iso
/
unix
/
volume22
/
auth
/
part01
/
README
< prev
Wrap
Text File
|
1990-04-29
|
4KB
|
98 lines
attachport - attach a server program to a TCP port
authtcp - create a locally authenticated TCP connection to an Internet host
authd - authentication server daemon
authuser - remote authentication library
This package provides two benefits. The first is a secure user-level
implementation of RFC 931, the Authentication Server; unless TCP itself
is compromised, it is impossible to forge mail or news between computers
supporting RFC 931. The second is a single, modular interface to TCP.
Programs written to work with authtcp and attachport don't even need to
be recompiled to run under a more comprehensive network security system
like Kerberos, as long the auth package is replaced.
attachport version 4.1, April 18, 1990.
Copyright (c) 1990, Daniel J. Bernstein.
All rights reserved.
authtcp version 2.1, April 18, 1990.
Copyright (c) 1990, Daniel J. Bernstein.
All rights reserved.
authd version 2.1, April 18, 1990.
Copyright (c) 1990, Daniel J. Bernstein.
All rights reserved.
authuser version 2.0, April 2, 1990.
Copyright (c) 1990, Daniel J. Bernstein
All rights reserved.
This distribution packaged April 18, 1990.
Files:
CHANGES Description of changes since first distributed version
README This document
Makefile Installation commands
attachport.c The attachport program
authtcp.c The authtcp program
authd.c The authd program
authuser.c The authuser library
attachport.man Documentation
authtcp.man Documentation
authd.man Documentation
authuser.man Documentation
djberr.h Error macros
djbatoi.h Replacement atoi()---Sun's library version can crash
dir.doc Description of authentication directory contents
rfc931 RFC 931, Authentication Server
Edit the options in Makefile and type make. attachport, authtcp, and
authd will be the executable programs; authuser.o will be the linkable
library; attachport.1, authtcp.1, authd.8, and authuser.3 will be the
nroff'ed documentation.
You probably want to pick up the multitee and authutil packages before
trying out any of these programs.
For authentication to work, you must set up a new userid, say auth.
Uid auth should not permit logins. Its encrypted password should be
something impossible, like an asterisk. Its shell should be /bin/true.
Its home directory should be /nonexistent. Its uid should be unique.
authtcp and attachport should be setuid auth; check the source carefully
for security holes! You also need a directory /usr/etc/auth/tcp, owner
auth, group irrelevant, mode 0700. (You can use a different directory/tcp
if you set AUTHDIR in the Makefile.)
authd should be set up under attachport(1) or inetd(8) to receive
connections on TCP port 113. It should not be setuid auth, though it
will always run as auth.
The authuser library needs no particular preparation; if you want to
make it available to users, put it into a library archive and copy
authuser.h to /usr/include.
I don't pretend to know your machine's setup so there's no make install.
Read CHANGES for a list of changes. Type authtcp -C and authtcp -W
for copyright and warranty information, authtcp -H for help. Similarly
for attachport and authd. For authuser, print authusercopyright[] and
authuserwarranty[] for copyright and warranty information, authuserhelp[]
for help.
Read dir.doc for a description of the authentication directory as used
by authtcp, attachport, and authd.
Some BSD variants (notably ULTRIX) handle multiple non-root setuid
processes poorly. To test the behavior of your system, try the
following sequence from a root csh:
SU% cp /usr/bin/sleep /tmp/slip
SU% chown nobody /tmp/slip; chmod 4755 /tmp/slip
SU% repeat 100 sh -ic '(/tmp/slip 10000 &) 2>&1' > /tmp/pids
SU% /bin/kill "`cat /tmp/pids`"
Here 100 is any number bigger than MAXUPRC in /usr/include/sys/param.h.
If the repeat fails, hangs, or crashes your system, complain at your
vendor: you can't reliably install programs setuid to anything except
root. In this case you'll have to install auth setuid root rather than
setuid auth as per the instructions; this is perfectly safe.