386BSD 0.1 development
[unix-history] / usr / src / usr.bin / rlogin / rlogin.1
CommitLineData
7b089094
WJ
1.\" Copyright (c) 1983, 1990 The Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
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.
19.\"
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
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)rlogin.1 6.19 (Berkeley) 7/27/91
33.\"
34.Dd July 27, 1991
35.Dt RLOGIN 1
36.Os BSD 4.2
37.Sh NAME
38.Nm rlogin
39.Nd remote login
40.Sh SYNOPSIS
41.Ar rlogin
42.Op Fl 8EKLdx
43.Op Fl e Ar char
44.Op Fl k Ar realm
45.Op Fl l Ar username
46.Ar host
47.Sh DESCRIPTION
48.Nm Rlogin
49starts a terminal session on a remote host
50.Ar host .
51.Pp
52.Nm Rlogin
53first attempts to use the Kerberos authorization mechanism, described below.
54If the remote host does not supporting Kerberos the standard Berkeley
55.Pa rhosts
56authorization mechanism is used.
57The options are as follows:
58.Bl -tag -width flag
59.It Fl 8
60The
61.Fl 8
62option allows an eight-bit input data path at all times; otherwise
63parity bits are stripped except when the remote side's stop and start
64characters are other than
65^S/^Q .
66.It Fl E
67The
68.Fl E
69option stops any character from being recognized as an escape character.
70When used with the
71.Fl 8
72option, this provides a completely transparent connection.
73.It Fl K
74The
75.Fl K
76option turns off all Kerberos authentication.
77.It Fl L
78The
79.Fl L
80option allows the rlogin session to be run in ``litout'' (see
81.Xr tty 4 )
82mode.
83.It Fl d
84The
85.Fl d
86option turns on socket debugging (see
87.Xr setsockopt 2 )
88on the TCP sockets used for communication with the remote host.
89.It Fl e
90The
91.Fl e
92option allows user specification of the escape character, which is
93``~'' by default.
94This specification may be as a literal character, or as an octal
95value in the form \ennn.
96.It Fl k
97The
98.FL k
99option requests rlogin to obtain tickets for the remote host
100in realm
101.Ar realm
102instead of the remote host's realm as determined by
103.Xr krb_realmofhost 3 .
104.It Fl x
105The
106.Fl x
107option turns on
108.Tn DES
109encryption for all data passed via the
110rlogin session.
111This may impact response time and
112.Tn CPU
113utilization, but provides
114increased security.
115.El
116.Pp
117A line of the form ``<escape char>.'' disconnects from the remote host.
118Similarly, the line ``<escape char>^Z'' will suspend the
119.Nm rlogin
120session, and ``<escape char><delayed-suspend char>'' suspends the
121send portion of the rlogin, but allows output from the remote system.
122By default, the tilde (``~'') character is the escape character, and
123normally control-Y (``^Y'') is the delayed-suspend character.
124.Pp
125All echoing takes place at the remote site, so that (except for delays)
126the
127.Nm rlogin
128is transparent.
129Flow control via ^S/^Q and flushing of input and output on interrupts
130are handled properly.
131.Sh KERBEROS AUTHENTICATION
132Each user may have a private authorization list in the file
133.Pa .klogin
134in their home directory.
135Each line in this file should contain a Kerberos principal name of the
136form
137.Ar principal.instance@realm .
138If the originating user is authenticated to one of the principals named
139in
140.Pa .klogin ,
141access is granted to the account.
142The principal
143.Ar accountname.@localrealm
144is granted access if
145there is no
146.Pa .klogin
147file.
148Otherwise a login and password will be prompted for on the remote machine
149as in
150.Xr login 1 .
151To avoid certain security problems, the
152.Pa .klogin
153file must be owned by
154the remote user.
155.Pp
156If Kerberos authentication fails, a warning message is printed and the
157standard Berkeley
158.Nm rlogin
159is used instead.
160.Sh ENVIRONMENT
161The following environment variable is utilized by
162.Nm rlogin :
163.Bl -tag -width TERM
164.It Ev TERM
165Determines the user's terminal type.
166.El
167.Sh SEE ALSO
168.Xr rsh 1 ,
169.Xr kerberos 3 ,
170.Xr krb_sendauth 3 ,
171.Xr krb_realmofhost 3
172.Sh HISTORY
173The
174.Nm rlogin
175command appeared in
176.Bx 4.2 .
177.Sh BUGS
178.Nm Rlogin
179will be replaced by
180.Xr telnet 1
181in the near future.
182.Pp
183More of the environment should be propagated.