1 .\" Copyright (c) 1983, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)telnetd.8 8.4 (Berkeley) 6/1/94
44 .Nm /usr/libexec/telnetd
53 .Op Fl debug Op Ar port
57 command is a server which supports the
61 virtual terminal protocol.
63 is normally invoked by the internet server (see
65 for requests to connect to the
67 port as indicated by the
73 option may be used to start up
75 manually, instead of through
77 If started up this way,
79 may be specified to run
87 command accepts the following options:
88 .Bl -tag -width indent
90 This option may be used for specifying what mode should
91 be used for authentication.
92 Note that this option is only useful if
94 has been compiled with support for the
97 There are several valid values for
101 Turn on authentication debugging code.
103 Only allow connections when the remote user
104 can provide valid authentication information
105 to identify the remote user,
106 and is allowed access to the specified account
107 without providing a password.
109 Only allow connections when the remote user
110 can provide valid authentication information
111 to identify the remote user.
114 command will provide any additional user verification
115 needed if the remote user is not allowed automatic
116 access to the specified account.
118 Only allow connections that supply some authentication information.
119 This option is currently not supported
120 by any of the existing authentication mechanisms,
121 and is thus the same as specifying
125 This is the default state.
126 Authentication information is not required.
127 If no or insufficient authentication information
128 is provided, then the
130 program will provide the necessary user
133 Disable the authentication code.
134 All user verification will happen through the
139 Specify bftp server mode. In this mode,
141 causes login to start a
143 session rather than the user's
144 normal shell. In bftp daemon mode normal
145 logins are not supported, and it must be used
146 on a port other than the normal
149 .It Fl D Ar debugmode
150 This option may be used for debugging purposes.
153 to print out debugging information
154 to the connection, allowing the user to see what
157 There are several possible values for
159 .Bl -tag -width exercise
161 Print information about the negotiation of
167 information, plus some additional information
168 about what processing is going on.
170 Display the data stream received by
173 Display data written to the pty.
175 Has not been implemented yet.
178 Enable debugging on each socket created by
187 has been compiled with support for data encryption, then the
189 option may be used to enable encryption debugging code.
191 Disable the printing of host-specific information before
192 login has been completed.
194 This option is only useful if
196 has been compiled with both linemode and kludge linemode
199 option is specified, then if the remote client does not
204 will operate in character at a time mode.
205 It will still support kludge linemode, but will only
206 go into kludge linemode if the remote client requests
208 (This is done by the client sending
209 .Dv DONT SUPPRESS-GO-AHEAD
214 option is most useful when there are remote clients
215 that do not support kludge linemode, but pass the heuristic
216 (if they respond with
220 for kludge linemode support.
222 Specify line mode. Try to force clients to use line-
226 option is not supported, it will go
227 into kludge linemode.
231 keep-alives. Normally
235 keep-alive mechanism to probe connections that
236 have been idle for some period of time to determine
237 if the client is still there, so that idle connections
238 from machines that have crashed or can no longer
239 be reached may be cleaned up.
240 .It Fl p Ar loginprog
243 command to run to complete the login. The alternate command must
244 understand the same command arguments as the standard login.
247 This option is used to specify the size of the field
250 structure that holds the remote host name.
251 If the resolved host name is longer than
253 the dotted decimal value will be used instead.
254 This allows hosts with very long host names that
255 overflow this field to still be uniquely identified.
258 indicates that only dotted decimal addresses
259 should be put into the
265 to refuse connections from addresses that
266 cannot be mapped back into a symbolic name
271 This option is only valid if
273 has been built with support for the authentication option.
274 It disables the use of
277 can be used to temporarily disable
278 a specific authentication type without having to recompile
283 operates by allocating a pseudo-terminal device (see
285 for a client, then creating a login process which has
286 the slave side of the pseudo-terminal as
292 manipulates the master side of the pseudo-terminal,
295 protocol and passing characters
296 between the remote client and the login process.
300 session is started up,
304 options to the client side indicating
305 a willingness to do the
308 options, which are described in more detail below:
309 .Bd -literal -offset indent
317 WILL SUPPRESS GO AHEAD
326 The pseudo-terminal allocated to the client is configured
336 has support for enabling locally the following
339 .Bl -tag -width "DO AUTHENTICATION"
347 will be sent to the client to indicate the
348 current state of terminal echoing.
349 When terminal echo is not desired, a
351 is sent to indicate that
353 will take care of echoing any data that needs to be
354 echoed to the terminal, and then nothing is echoed.
355 When terminal echo is desired, a
357 is sent to indicate that
359 will not be doing any terminal echoing, so the
360 client should do any terminal echoing that is needed.
362 Indicate that the client is willing to send a
363 8 bits of data, rather than the normal 7 bits
364 of the Network Virtual Terminal.
366 Indicate that it will not be sending
370 Indicate a willingness to send the client, upon
371 request, of the current status of all
374 .It "WILL TIMING-MARK"
377 command is received, it is always responded
379 .Dv WILL TIMING-MARK .
385 is sent in response, and the
387 session is shut down.
391 is compiled with support for data encryption, and
392 indicates a willingness to decrypt
397 has support for enabling remotely the following
400 .Bl -tag -width "DO AUTHENTICATION"
402 Sent to indicate that
404 is willing to receive an 8 bit data stream.
406 Requests that the client handle flow control
409 This is not really supported, but is sent to identify a
412 client, which will improperly respond with
418 will be sent in response.
419 .It "DO TERMINAL-TYPE"
420 Indicate a desire to be able to request the
421 name of the type of terminal that is attached
422 to the client side of the connection.
424 Indicate that it does not need to receive
426 the go ahead command.
428 Requests that the client inform the server when
429 the window (display) size changes.
430 .It "DO TERMINAL-SPEED"
431 Indicate a desire to be able to request information
432 about the speed of the serial line to which
433 the client is attached.
435 Indicate a desire to be able to request the name
436 of the X Window System display that is associated with
439 Indicate a desire to be able to request environment
440 variable information, as described in RFC 1572.
442 Indicate a desire to be able to request environment
443 variable information, as described in RFC 1408.
447 is compiled with support for linemode, and
448 requests that the client do line by line processing.
452 is compiled with support for both linemode and
453 kludge linemode, and the client responded with
455 If the client responds with
457 the it is assumed that the client supports
461 option can be used to disable this.
462 .It "DO AUTHENTICATION"
465 is compiled with support for authentication, and
466 indicates a willingness to receive authentication
467 information for automatic login.
471 is compiled with support for data encryption, and
472 indicates a willingness to decrypt
485 and use that information (if present) to determine
486 what to display before the login: prompt. You can
487 also use a System V style
491 capability, which will override
493 The information specified in either
497 will be displayed to both console and remote logins.
500 .Bl -tag -width /usr/ucb/bftp -compact
515 .Bl -tag -compact -width RFC-1572
518 PROTOCOL SPECIFICATION
520 TELNET OPTION SPECIFICATIONS
522 TELNET BINARY TRANSMISSION
526 TELNET SUPPRESS GO AHEAD OPTION
530 TELNET TIMING MARK OPTION
532 TELNET EXTENDED OPTIONS - LIST OPTION
534 TELNET END OF RECORD OPTION
536 Telnet Window Size Option
538 Telnet Terminal Speed Option
540 Telnet Terminal-Type Option
542 Telnet X Display Location Option
544 Requirements for Internet Hosts -- Application and Support
546 Telnet Linemode Option
548 Telnet Remote Flow Control Option
550 Telnet Authentication Option
552 Telnet Authentication: Kerberos Version 4
554 Telnet Authentication: SPX
556 Telnet Environment Option Interoperability Issues
558 Telnet Environment Option
563 commands are only partially implemented.
565 Because of bugs in the original
569 performs some dubious protocol exchanges to try to discover if the remote
570 client is, in fact, a
575 has no common interpretation except between similar operating systems
578 The terminal type name received from the remote client is converted to
587 IPv6 support was added by WIDE/KAME project.