updates
[unix-history] / usr / src / libexec / fingerd / fingerd.8
CommitLineData
e6b338bd
KM
1.\" Copyright (c) 1980 Regents of the University of California.
2.\" All rights reserved. The Berkeley software License Agreement
3.\" specifies the terms and conditions for redistribution.
4.\"
5.\" @(#)fingerd.8 6.1 (Berkeley) %G%
6.\"
7.TH FINGERD 8C ""
8.UC 6
9.SH NAME
10fingerd \- remote user information server
11.SH SYNOPSIS
12.B /etc/fingerd
13.SH DESCRIPTION
14.I Fingerd
15is a simple protocol based on RFC742 that provides an interface to the
16Name and Finger programs at several network sites.
17The program is supposed to return a friendly,
18human-oriented status report on either the system at the moment
19or a particular person in depth.
20There is no required format and the
21protocol consists mostly of specifying a single ``command line''.
22.PP
23.I Fingerd
24listens for TCP requests at port 79.
25Once connected it reads a single command line
26terminated by a <CRLF> which is passed to
27.IR finger (1).
28.I Fingerd
29closes its connections as soon as the output is finished.
30.PP
31If the line is null (i.e. just a <CRLF> is sent) then
32.I finger
33returns a ``default'' report that lists all people logged into
34the system at that moment.
35.PP
36If a user name is specified (e.g. eric<CRLF>) then the
37response lists more extended information for only that particular user,
38whether logged in or not.
39Allowable ``names'' in the command line include both ``login names''
40and ``user names''.
41If a name is ambiguous, all possible derivations are returned.
42.SH SEE ALSO
43finger(1)
44.SH BUGS
45Connecting directly to the server from a TIP
46or an equally narrow-minded TELNET-protocol user program can result
47in meaningless attempts at option negotiation being sent to the
48server, which will foul up the command line interpretation.
49.I Fingerd
50should be taught to filter out IAC's and perhaps even respond
51negatively (IAC WON'T) to all option commands received.