fingerd implements the server side of the Name/Finger protocol, 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 connected, 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.
fingerd supports the following option.
Enable secure mode. Deny forwarding of queries to other remote hosts.
User and accounting information.
System password file.
Last login times.
fingerd and in.fingerd are IPv6–enabled. See ip6(7P).
See attributes(5) for descriptions of the following attributes:
Harrenstien, Ken, RFC 742, NAME/FINGER, Network Information Center, SRI International, Menlo Park, Calif., December 1977.
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 foul up the command line interpretation. fingerd should be taught to filter out IAC's and perhaps even respond negatively (IAC does not) to all option commands received.
The in.fingerd service is managed by the service management facility, smf(5), under the service identifier:
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). Responsibility for initiating and restarting this service is delegated to inetd(1M). Use inetadm(1M) to make configuration changes and to view configuration information for this service. The service's status can be queried using the svcs(1) command.