.\" Copyright (c) 1983 The Regents of the University of California.
.\" Redistribution and use in source and binary forms are permitted
.\" provided that the above copyright notice and this paragraph are
.\" duplicated in all such forms and that any documentation,
.\" advertising materials, and other materials related to such
.\" distribution and use acknowledge that the software was developed
.\" by the University of California, Berkeley. The name of the
.\" University may not be used to endorse or promote products derived
.\" from this software without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
.\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
.\" @(#)telnetd.8 6.5 (Berkeley) %G%
telnetd \- DARPA TELNET protocol server
is a server which supports the DARPA standard
virtual terminal protocol.
is invoked by the internet server (see
normally for requests to connect to the
operates by allocating a pseudo-terminal device (see
for a client, then creating a login process which has
the slave side of the pseudo-terminal as
manipulates the master side of the pseudo-terminal,
protocol and passing characters
between the remote client and the login process.
options to the client side indicating
.I window size information
If the remote client is willing, the remote terminal type is
propagated in the environment of the created login process.
The pseudo-terminal allocated to the client is configured
to operate in \*(lqcooked\*(rq mode, and with XTABS and CRMOD
is willing to have the remote client
commands are only partially implemented.
Because of bugs in the original 4.2 BSD
performs some dubious protocol exchanges to try to discover if the remote
client is, in fact, a 4.2 BSD
has no common interpretation except between similar operating systems
The terminal type name received from the remote client is converted to