--- users_guide.orig Sun Jun 18 13:26:54 2000 +++ users_guide Sun Dec 8 15:14:01 2002 @@ -166,7 +166,10 @@ crimelab.com but now it appears the only source is ftp.bellcore.com. I suggest you try a web search for s/key source code. -Note: S/KEY is a trademark of Bell Communications Research (Bellcore). +To use OPIE, you must have built tac_plus with the -DWITH_OPIE flag. + +Note: S/KEY and OPIE are a trademark of Bell Communications Research +(Bellcore). Should you need them, there are routines for accessing password files (getpwnam,setpwent,endpwent,setpwfile) in pw.c. @@ -436,6 +439,15 @@ login = skey } +4. Authentication using opie. + +If you have successfully built tac_plus with opie support, you can specify +a user be authenticated via opie, as follows: + + user = marcus { + login = opie + } + RECURSIVE PASSWORD LOOKUPS --------------------------- @@ -1370,7 +1382,7 @@ and then send the daemon a SIGUSR1. This will cause it to reinitialize itself and re-read the configuration file. -On startup, tac_plus creates the file /etc/tac_plus.pid , if possible, +On startup, tac_plus creates the file /var/run/tac_plus.pid , if possible, containing its process id. If you invoke the daemon so that it listens on a non-standard port, the file created is /etc/tac_plus.pid.<port> instead, where <port> is the port number the daemon is listening on. @@ -1378,7 +1390,7 @@ Assuming you are listening on the default port 49, something like the following should work: -# kill -USR1 `cat /etc/tac_plus.pid` +# kill -USR1 `cat /var/run/tac_plus.pid` It's a good idea to check that the daemon is still running after sending it a SIGUSR1, since a syntactically incorrect configuration