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.
5 .\" @(#)fingerd.8c 6.1 (Berkeley) 5/23/86
7 .TH FINGERD 8 "May 23, 1986"
10 fingerd, in.fingerd \- remote user information server
12 .B "finger stream tcp nowait nobody /usr/sbin/in.fingerd in.fingerd"
14 .B "tcpd finger /usr/sbin/in.fingerd in.fingerd"
17 is a simple protocol based on RFC742 that provides an interface to the
18 Name and Finger programs at several network sites.
19 The program is supposed to return a friendly,
20 human-oriented status report on either the system at the moment
21 or a particular person in depth.
22 There is no required format and the
23 protocol consists mostly of specifying a single ``command line''.
26 listens for TCP requests at port 79.
27 Once connected it reads a single command line
28 terminated by a <CRLF> which is passed to
31 closes its connections as soon as the output is finished.
33 If the line is null (i.e. just a <CRLF> is sent) then
35 returns a ``default'' report that lists all people logged into
36 the system at that moment.
38 If a user name is specified (e.g. eric<CRLF>) then the
39 response lists more extended information for only that particular user,
40 whether logged in or not.
41 Allowable ``names'' in the command line include both ``login names''
43 If a name is ambiguous, all possible derivations are returned.
47 Connecting directly to the server from a TIP
48 or an equally narrow-minded TELNET-protocol user program can result
49 in meaningless attempts at option negotiation being sent to the
50 server, which will foul up the command line interpretation.
52 should be taught to filter out IAC's and perhaps even respond
53 negatively (IAC WON'T) to all option commands received.