|
|
1.1 root 1: .TH TELNETD 8C "4 March 1983"
2: .UC 4
3: .SH NAME
4: telnetd \- DARPA TELNET protocol server
5: .SH SYNOPSIS
6: .B /etc/telnetd
7: [
8: .B \-d
9: ] [
10: .I port
11: ]
12: .SH DESCRIPTION
13: .I Telnetd
14: is a server which supports the DARPA standard TELNET
15: virtual terminal protocol. The TELNET server operates
16: at the port indicated in the ``telnet'' service description;
17: see
18: .IR services (5).
19: This port number may be overridden (for debugging purposes)
20: by specifying a port number on the command line. If the
21: .B \-d
22: option is specified, each socket created by
23: .I telnetd
24: will have debugging enabled (see SO_DEBUG in
25: .IR socket (2)).
26: .PP
27: .I Telnetd
28: operates by allocating a pseudo-terminal device (see
29: .IR pty (4))
30: for a client, then creating a login process which has
31: the slave side of the pseudo-terminal as
32: .BR stdin ,
33: .BR stdout ,
34: and
35: .BR stderr .
36: .I Telnetd
37: manipulates the master side of the pseudo terminal,
38: implementing the TELNET protocol and passing characters
39: between the client and login process.
40: .PP
41: When a TELNET session is started up,
42: .I telnetd
43: sends a TELNET option to the client side indicating
44: a willingness to do ``remote echo'' of characters.
45: The pseudo terminal allocated to the client is configured
46: to operate in ``cooked'' mode, and with XTABS and CRMOD
47: enabled (see
48: .IR tty (4)).
49: Aside from this initial setup, the only mode changes
50: .I telnetd
51: will carry out are those required for echoing characters
52: at the client side of the connection.
53: .PP
54: .I Telnetd
55: supports binary mode, and most of the common TELNET options,
56: but does not, for instance, support timing marks. Consult
57: the source code for an exact list of which options are not
58: implemented.
59: .SH "SEE ALSO"
60: telnet(1C)
61: .SH BUGS
62: .I Telnetd
63: supports at most 16 users. It uses these
64: pseudo-terminals
65: /dev/ptyp[0-9a-f].
66: .PP
67: A complete list of the options supported should be given here.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.