1 .\" $NetBSD: telnetd.8,v 1.30 2004/07/17 18:34:01 wiz Exp $
3 .\" Copyright (c) 1983, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
9 .\" 1. Redistributions of source code must retain the above copyright
10 .\" notice, this list of conditions and the following disclaimer.
11 .\" 2. Redistributions in binary form must reproduce the above copyright
12 .\" notice, this list of conditions and the following disclaimer in the
13 .\" documentation and/or other materials provided with the distribution.
14 .\" 3. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30 .\" from: @(#)telnetd.8 8.3 (Berkeley) 3/1/94
41 .Nm /usr/libexec/telnetd
50 .Op Fl debug Op Ar port
54 command is a server which supports the
58 virtual terminal protocol.
60 is normally invoked by the internet server (see
62 for requests to connect to the
64 port as indicated by the
70 option may be used to start up
72 manually, instead of through
74 If started up this way,
76 may be specified to run
84 command accepts the following options:
85 .Bl -tag -width "-a authmode"
87 This option may be used for specifying what mode should
88 be used for authentication.
89 Note that this option is only useful if
91 has been compiled with support for the
94 There are several valid values for
98 Turns on authentication debugging code.
100 Only allow connections when the remote user
101 can provide valid authentication information
102 to identify the remote user,
103 and is allowed access to the specified account
104 without providing a password.
106 Only allow connections when the remote user
107 can provide valid authentication information
108 to identify the remote user.
111 command will provide any additional user verification
112 needed if the remote user is not allowed automatic
113 access to the specified account.
115 Only allow connections that supply some authentication information.
116 This option is currently not supported
117 by any of the existing authentication mechanisms,
118 and is thus the same as specifying
122 This is the default state.
123 Authentication information is not required.
124 If no or insufficient authentication information
125 is provided, then the
127 program will provide the necessary user
130 This disables the authentication code.
131 All user verification will happen through the
135 .It Fl D Ar debugmode
136 This option may be used for debugging purposes.
139 to print out debugging information
140 to the connection, allowing the user to see what
143 There are several possible values for
145 .Bl -tag -width exercise
147 Prints information about the negotiation of
153 information, plus some additional information
154 about what processing is going on.
156 Displays the data stream received by
159 Displays data written to the pty.
161 Has not been implemented yet.
164 Enables debugging on each socket created by
173 has been compiled with support for data encryption, then the
175 option may be used to enable encryption debugging code.
177 Specifies which entry from
179 should be used to get banner strings, login program and
184 Disables the printing of host-specific information before
185 login has been completed.
187 This option is only useful if
189 has been compiled with both linemode and kludge linemode support.
193 then if the remote client does not support the
197 will operate in character at a time mode.
198 It will still support kludge linemode, but will only
199 go into kludge linemode if the remote client requests it.
200 (This is done by by the client sending
201 .Dv DONT SUPPRESS-GO-AHEAD
206 option is most useful when there are remote clients
207 that do not support kludge linemode, but pass the heuristic
208 (if they respond with
212 for kludge linemode support.
215 Tries to force clients to use line-at-a-time mode.
218 option is not supported, it will go
219 into kludge linemode.
228 keep-alive mechanism to probe connections that
229 have been idle for some period of time to determine
230 if the client is still there, so that idle connections
231 from machines that have crashed or can no longer
232 be reached may be cleaned up.
234 This option is only enabled if
236 is compiled with support for secure logins.
239 option to be passed on to
241 and thus is only useful if
245 flag to indicate that only Kerberos or S/Key
246 validated logins are allowed, and is
247 usually useful for controlling remote logins
248 from outside of a firewall.
250 This option sets the IP Type-of Service (TOS) option
251 on the connection to the value tos, which may be a
252 numeric TOS value or a symbolic TOS name found in the
255 This option has no effect on
257 .\"The option has no effect on systems that do not
264 This option is used to specify the size of the field
267 structure that holds the remote host name.
268 If the resolved host name is longer than
270 the dotted decimal value will be used instead.
271 This allows hosts with very long host names that
272 overflow this field to still be uniquely identified.
275 indicates that only dotted decimal addresses
276 should be put into the
282 to refuse connections from addresses that
283 cannot be mapped back into a symbolic name via the
287 This option is only valid if
289 has been built with support for the authentication option.
290 It disables the use of
292 authentication, and can be used to temporarily disable
293 a specific authentication type without having to recompile
297 Specifies address family to be used on
300 During normal operation
306 will use the file descriptor passed from
311 operates by allocating a pseudo-terminal device (see
313 for a client, then creating a login process which has
314 the slave side of the pseudo-terminal as
320 manipulates the master side of the pseudo-terminal,
323 protocol and passing characters
324 between the remote client and the login process.
328 session is started up,
332 options to the client side indicating
333 a willingness to do the following
335 options, which are described in more detail below:
336 .Bd -literal -offset indent
344 WILL SUPPRESS GO AHEAD
353 The pseudo-terminal allocated to the client is configured
354 to operate in \*(lqcooked\*(rq mode, and with
361 has support for enabling locally the following
364 .Bl -tag -width "DO AUTHENTICATION"
372 will be sent to the client to indicate the
373 current state of terminal echoing.
374 When terminal echo is not desired, a
376 is sent to indicate that
378 will take care of echoing any data that needs to be
379 echoed to the terminal, and then nothing is echoed.
380 When terminal echo is desired, a
382 is sent to indicate that
384 will not be doing any terminal echoing, so the
385 client should do any terminal echoing that is needed.
387 Indicates that the client is willing to send a
388 8 bits of data, rather than the normal 7 bits
389 of the Network Virtual Terminal.
391 Indicates that it will not be sending
395 Indicates a willingness to send the client, upon
396 request, of the current status of all
399 .It "WILL TIMING-MARK"
402 command is received, it is always responded
410 is sent in response, and the
412 session is shut down.
416 is compiled with support for data encryption, and
417 indicates a willingness to decrypt the data stream.
421 has support for enabling remotely the following
424 .Bl -tag -width "DO AUTHENTICATION"
426 Sent to indicate that
428 is willing to receive an 8 bit data stream.
430 Requests that the client handle flow control
433 This is not really supported, but is sent to identify a
436 client, which will improperly respond with
442 will be sent in response.
443 .It "DO TERMINAL-TYPE"
444 Indicates a desire to be able to request the
445 name of the type of terminal that is attached
446 to the client side of the connection.
448 Indicates that it does not need to receive
450 the go ahead command.
452 Requests that the client inform the server when
453 the window (display) size changes.
454 .It "DO TERMINAL-SPEED"
455 Indicates a desire to be able to request information
456 about the speed of the serial line to which
457 the client is attached.
459 Indicates a desire to be able to request the name
460 of the X windows display that is associated with
463 Indicates a desire to be able to request environment
464 variable information, as described in RFC 1572.
466 Indicates a desire to be able to request environment
467 variable information, as described in RFC 1408.
471 is compiled with support for linemode, and
472 requests that the client do line by line processing.
476 is compiled with support for both linemode and
477 kludge linemode, and the client responded with
479 If the client responds with
481 the it is assumed that the client supports kludge linemode.
484 option can be used to disable this.
485 .It "DO AUTHENTICATION"
488 is compiled with support for authentication, and
489 indicates a willingness to receive authentication
490 information for automatic login.
494 is compiled with support for data encryption, and
495 indicates a willingness to decrypt the data stream.
498 At the end of a login session,
502 facility with an action of "telnetd" and user "root"
503 to execute site-specific commands.
518 .Bl -tag -compact -width "RFC 1572 "
521 PROTOCOL SPECIFICATION
523 TELNET OPTION SPECIFICATIONS
525 TELNET BINARY TRANSMISSION
529 TELNET SUPPRESS GO AHEAD OPTION
533 TELNET TIMING MARK OPTION
535 TELNET EXTENDED OPTIONS - LIST OPTION
537 TELNET END OF RECORD OPTION
539 Telnet Window Size Option
541 Telnet Terminal Speed Option
543 Telnet Terminal-Type Option
545 Telnet X Display Location Option
547 Requirements for Internet Hosts -- Application and Support
549 Telnet Linemode Option
551 Telnet Remote Flow Control Option
553 Telnet Authentication Option
555 Telnet Authentication: Kerberos Version 4
557 Telnet Authentication: SPX
559 Telnet Environment Option Interoperability Issues
561 Telnet Environment Option
566 commands are only partially implemented.
568 Because of bugs in the original
572 performs some dubious protocol exchanges to try to discover if the remote
573 client is, in fact, a
578 has no common interpretation except between similar operating systems
584 The terminal type name received from the remote client is converted to