2 .\" Copyright 1989 AT&T
3 .\" Copyright (C) 2008, Sun Microsystems, Inc. All Rights Reserved
4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH RLOGIN 1 "Dec 23, 2008"
13 \fBrlogin\fR [\fB-8EL\fR] [\fB-e\fIc\fR\fR ] [\fB-A\fR] [\fB-K\fR] [\fB-x\fR] [\fB-PN\fR | \fB-PO\fR] [\fB-f\fR | \fB-F\fR] [\fB-a\fR]
14 [\fB-l\fR \fIusername\fR] [\fB-k\fR \fIrealm\fR] \fIhostname\fR
20 The \fBrlogin\fR utility establishes a remote login session from your terminal
21 to the remote machine named \fIhostname\fR. The user can choose to kerberize
22 the rlogin session using Kerberos V5 and also protect the data being
26 Hostnames are listed in the \fIhosts\fR database, which can be contained in the
27 \fB/etc/hosts\fR file, the Network Information Service (\fBNIS\fR) \fBhosts\fR
28 map, the Internet domain name server, or a combination of these. Each host has
29 one official name (the first name in the database entry), and optionally one or
30 more nicknames. Either official hostnames or nicknames can be specified in
34 The user can opt for a secure rlogin session which uses Kerberos V5 for
35 authentication. Encryption of the session data is also possible. The rlogin
36 session can be kerberized using any of the following Kerberos specific options:
37 \fB-A\fR, \fB-PN\fR or \fB-PO\fR, \fB-x\fR, \fB-f\fR or \fB-F\fR, and \fB-k\fR
38 \fIrealm\fR. Some of these options (\fB-A\fR, \fB-x\fR, \fB-PN\fR or \fB-PO\fR,
39 and \fB-f\fR or \fB-F\fR) can also be specified in the \fB[appdefaults]\fR
40 section of \fBkrb5.conf\fR(4). The usage of these options and the expected
41 behavior is discussed in the OPTIONS section below. If Kerberos authentication
42 is used, authorization to the account is controlled through rules in
43 \fBkrb5_auth_rules\fR(5). If this authorization fails, fallback to normal
44 \fBrlogin\fR using \fBrhosts\fR occurs only if the \fB-PO\fR option is used
45 explicitly on the command line or is specified in \fBkrb5.conf\fR(4). Also
46 notice that the \fB-PN\fR or \fB-PO\fR, \fB-x\fR, \fB-f\fR or \fB-F\fR, and
47 \fB-k\fR \fIrealm\fR options are just supersets of the \fB-A\fR option.
50 The remote terminal type is the same as your local terminal type, as given in
51 your environment \fBTERM\fR variable. The terminal or window size is also
52 copied to the remote system if the server supports the option. Changes in size
53 are reflected as well. All echoing takes place at the remote site, so that
54 (except for delays) the remote login is transparent. Flow control using
55 Control-S and Control-Q and flushing of input and output on interrupts are
60 The following options are supported:
67 Passes eight-bit data across the net instead of seven-bit data.
76 Forces the remote machine to ask for a password by sending a null local
86 Explicitly enables Kerberos authentication and trusts the \fB\&.k5login\fR file
87 for access-control. If the authorization check by \fBin.rlogind\fR(1M) on the
88 server-side succeeds and if the \fB\&.k5login\fR file permits access, the user
89 is allowed to login without supplying a password.
98 Specifies a different escape character, \fIc\fR, for the line used to
99 disconnect from the remote host.
108 Stops any character from being recognized as an escape character.
117 Forwards a copy of the local credentials (Kerberos Ticket Granting Ticket) to
118 the remote system. This is a non-forwardable ticket granting ticket. You must
119 forward a ticket granting ticket if you need to authenticate yourself to other
120 Kerberized network services on the remote host. An example is if your home
121 directory on the remote host is \fBNFS\fR mounted via Kerberos V5. If your
122 local credentials are not forwarded in this case, you can not access your home
123 directory. This option is mutually exclusive with the \fB-F\fR option.
132 Forwards a forwardable copy of the local credentials (Kerberos Ticket Granting
133 Ticket) to the remote system. The \fB-F\fR option provides a superset of the
134 functionality offered by the \fB-f\fR option. For example, with the \fB-f\fR
135 option, after you connected to the remote host, any attempt to invoke
136 \fB/usr/bin/ftp\fR, \fB/usr/bin/telnet\fR, \fB/usr/bin/rlogin\fR, or
137 \fB/usr/bin/rsh\fR with the \fB-f\fR or \fB-F\fR options would fail. Thus, you
138 would be unable to push your single network sign on trust beyond one system.
139 This option is mutually exclusive with the \fB-f\fR option.
145 \fB\fB-k\fR \fIrealm\fR\fR
148 Causes \fBrlogin\fR to obtain tickets for the remote host in \fIrealm\fR
149 instead of the remote host's realm as determined by \fBkrb5.conf\fR(4).
158 This option explicitly disables Kerberos authentication. It can be used to
159 override the \fBautologin\fR variable in \fBkrb5.conf\fR(4).
165 \fB\fB-l\fR \fIusername\fR\fR
168 Specifies a different \fIusername\fR for the remote login. If you do not use
169 this option, the remote username used is the same as your local username.
178 Allows the rlogin session to be run in "\fBlitout\fR" mode.
191 Explicitly requests the new (\fB-PN\fR) or old (\fB-PO\fR) version of the
192 Kerberos `\fBrcmd\fR' protocol. The new protocol avoids many security problems
193 prevalant in the old one and is considered much more secure, but is not
194 interoperable with older (MIT/SEAM) servers. The new protocol is used by
195 default, unless explicitly specified using these options or by using
196 \fBkrb5.conf\fR(4). If Kerberos authorization fails when using the old
197 `\fBrcmd\fR' protocol, there is fallback to regular, non-kerberized
198 \fBrlogin\fR. This is not the case when the new, more secure `\fBrcmd\fR'
208 Turns on \fBDES\fR encryption for all data passed through the rlogin session.
209 This reduces response time and increases \fBCPU\fR utilization.
212 .SS "Escape Sequences"
215 Lines that you type which start with the tilde character (\fB~\fR) are "escape
216 sequences." The escape character can be changed using the \fB-e\fR option.
223 Disconnects from the remote host. This is not the same as a logout, because the
224 local host breaks the connection with no warning to the remote end.
233 Suspends the login session, but only if you are using a shell with Job Control.
234 \fBsusp\fR is your "suspend" character, usually Control-Z. See \fBtty\fR(1).
243 Suspends the input half of the login, but output is still able to be seen (only
244 if you are using a shell with Job Control). \fBdsusp\fR is your "deferred
245 suspend" character, usually Control-Y. See \fBtty\fR(1).
255 The remote machine on which \fIrlogin\fR establishes the remote login session.
261 For the kerberized rlogin session, each user can have a private authorization
262 list in a file, \fB\&.k5login\fR, in his home directory. Each line in this file
263 should contain a Kerberos principal name of the form
264 \fIprincipal\fR/\fIinstance@realm\fR. If there is a \fB~/.k5login\fR file,
265 access is granted to the account if and only if the originating user is
266 authenticated to one of the principals named in the \fB~/.k5login\fR file.
267 Otherwise, the originating user is granted access to the account if and only if
268 the authenticated principal name of the user can be mapped to the local account
269 name using the \fIauthenticated-principal-name\fR \(-> \fIlocal-user-name\fR
270 mapping rules. The \fB\&.k5login\fR file (for access control) comes into play
271 only when Kerberos authentication is being done.
274 For the non-secure rlogin session, each remote machine can have a file named
275 \fB/etc/hosts.equiv\fR containing a list of trusted host names with which it
276 shares user names. Users with the same user name on both the local and remote
277 machine can \fBrlogin\fR from the machines listed in the remote machine's
278 \fB/etc/hosts.equiv\fR file without supplying a password. Individual users
279 camayn set up a similar private equivalence list with the file \fB\&.rhosts\fR
280 in their home directories. Each line in this file contains two names, that is,
281 a host name and a user name, separated by a space. An entry in a remote user's
282 \fB\&.rhosts\fR file permits the user named \fIusername\fR who is logged into
283 \fIhostname\fR to log in to the remote machine as the remote user without
284 supplying a password. If the name of the local host is not found in the
285 \fB/etc/hosts.equiv\fR file on the remote machine, and the local user name and
286 host name are not found in the remote user's .\fBrhosts\fR file, then the
287 remote machine prompts for a password. Host names listed in the
288 \fB/etc/hosts.equiv\fR and \fB\&.rhosts\fR files must be the official host
289 names listed in the \fBhosts\fR database. Nicknames can not be used in either
293 For security reasons, the \fB\&.rhosts\fR file must be owned by either the
294 remote user or by root.
299 \fB\fB/etc/passwd\fR\fR
302 Contains information about users' accounts.
308 \fB\fB/usr/hosts/*\fR\fR
311 For \fIhostname\fR version of the command.
317 \fB\fB/etc/hosts.equiv\fR\fR
320 List of trusted hostnames with shared user names.
326 \fB\fB/etc/nologin\fR\fR
329 Message displayed to users attempting to login during machine shutdown.
335 \fB\fB$HOME/.rhosts\fR\fR
338 Private list of trusted hostname/username combinations.
344 \fB\fB$HOME/.k5login\fR\fR
347 File containing Kerberos principals that are allowed access.
353 \fB\fB/etc/krb5/krb5.conf\fR\fR
356 Kerberos configuration file.
362 \fB\fB/etc/hosts\fR\fR
371 \fBrsh\fR(1), \fBstty\fR(1), \fBtty\fR(1), \fBin.rlogind\fR(1M),
372 \fBhosts\fR(4),\fBhosts.equiv\fR(4), \fBkrb5.conf\fR(4), \fBnologin\fR(4),
373 \fBattributes\fR(5), \fBkrb5_auth_rules\fR(5)
377 The following message indicates that the machine is in the process of being
378 shutdown and logins have been disabled:
382 NO LOGINS: System going down in \fIN\fR \fBminutes\fR
390 When a system is listed in \fBhosts.equiv\fR, its security must be as good as
391 local security. One insecure system listed in \fBhosts.equiv\fR can compromise
392 the security of the entire system.
395 The Network Information Service (\fBNIS\fR) was formerly known as Sun Yellow
396 Pages (\fBYP\fR.) The functionality of the two remains the same. Only the name
400 This implementation can only use the \fBTCP\fR network service.