in.fingerd(1M)

NAME

     in.fingerd, fingerd - remote user information server

SYNOPSIS

     /usr/sbin/in.fingerd

DESCRIPTION

     fingerd implements the server side of the Name/Finger proto-
     col, specified in RFC 742. The Name/Finger protocol provides
     a remote interface to programs which display information  on
     system  status  and  individual  users. The protocol imposes
     little structure on  the  format  of  the  exchange  between
     client and server. The client provides a single command line
     to the finger server which returns a printable reply.

     fingerd waits for connections on  TCP  port  79.  Once  con-
     nected,  it  reads  a  single  command  line  terminated  by
     RETURN-LINEFEED  and  passes  the  arguments  to  finger(1),
     prepended with -s. fingerd closes its connections as soon as
     the output is finished.

     You must invoke fingerd from inetd.  See  inetd(1M) for more
     information.

FILES

      /var/adm/utmpx
           User and accounting information.

     /etc/passwd
           System password file.

     /var/adm/lastlog
           Last login times.

     $HOME/.plan
           User's plans.

     $HOME/.project
           User's projects.

USAGE

     fingerd and in.fingerd are IPv6-enabled.  See ip6(7P).

ATTRIBUTES

     See attributes(5) for descriptions of the  following  attri-
     butes:

     ____________________________________________________________
    |       ATTRIBUTE TYPE        |       ATTRIBUTE VALUE       |
    |_____________________________|_____________________________|
    | Availability                | SUNWrcmds                   |
    |_____________________________|_____________________________|

SEE ALSO

     finger(1), inetd(1M), inetd.conf(4), attributes(5), ip6(7P)

     Harrenstien, Ken, RFC 742, NAME/FINGER,  Network Information
     Center,  SRI  International,  Menlo  Park,  Calif., December
     1977.

NOTES

     Connecting directly to the server from a TIP or  an  equally
     narrow-minded  TELNET-protocol  user  program  can result in
     meaningless attempts at option negotiation being sent to the
     server,  which will foul up the command line interpretation.
     fingerd should be taught to filter  out  IAC's  and  perhaps
     even  respond  negatively (IAC will not)  to all option com-
     mands received.