Finger server and CMS client Dave Elbon University of Kentucky Fingserv Distribution June 1996 Fingserv is our VM/CMS server for the popular Internet Finger protocol (see RFC 1288). Also included here is our CMS Finger client. Both are written in REXX and make use of Rxsockets, pipes, and several of our own utilities (available separately). Some consider a Finger-type service a security exposure since it allows anyone to verify the existence of a userid. Depending on the features of our server enabled it can also reveal additional information. Foneserv uses the following files: FINGSERV EXEC -the server FINGSERV PARMS -the parameters FINGINFO EXEC -exit routine called by Fingserv to get the last system access time and user's name associated with a userid. Our sample version uses ACF2 and links to the userid looking for a Names file. FINGMAIL EXEC -exit routine called by Fingserv to determine if user has mail waiting FINGPLAN EXEC -exit routine called by Fingserv to get a user's PLAN FILE FINGSTAT EXEC -exit routine called by Fingserv to get a user's mail service status. We aren't using this - we are using Fingserv's built-in support for Listserv and Lmail. FINGTERM EXEC -exit routine called by Fingserv to get information about user's terminal. Our sample uses Netstat to get information about TCP/IP connections. The information returned by Fingserv and the exits called are determined by the FINGSERV PARMS file. Here's a sample: Authorize operator maint <- who can send commands to the server Default info mail plan stat term <- default response includes these (long request gets more information) Info on <- call FINGINFO Mail on <- call FINGMAIL Plan on <- call FINGPLAN Stat off <- don't call FINGSTAT Listserv on <- Look at Listserv FORWARD FILE Lmail on <- Look at Lmail USERPREF DATA Term on <- call FINGTERM FINGSERV requires class B for the MSGNOH command. Our FINGINFO exit requires authorization to link to any minidisk and to examine ACF2 logonid records. Our FINGMAIL exit requires class D to check spool files. The Listserv and Lmail functions require the ability to link to the LISTSERV and MAILER disks. None of our exits support SFS, since we just got rid of it. The TCPIP configuration file requires information like this describing the FINGER userid: FINGER password ; Finger server ... 79 TCP FINGER ; Finger server The userid of the server need not be FINGER and it is possible to run several copies of Fingserv in different virtual machines if the load requires it. Each server must be listed in the TCPIP config file. Our FINGER VM is 32 meg because it keeps our rather large Lmail prefs file in storage. We are currently running Foneserv under VM/ESA 2.2 and CMS 8. There is, of course, no warranty. Dave Elbon University of Kentucky Computing Center 128 McVey Hall Lexington, KY 40506-0045 USA Phone: 606 257.2230 E-mail: sysdave@ukcc.uky.edu