RLOGIN(1) OpenBSD Reference Manual RLOGIN(1)
NAME
rlogin - remote login
SYNOPSIS
rlogin [-8EKLd] [-e char] [-k realm] [-l username] host
DESCRIPTION
rlogin starts a terminal session on a remote host host.
rlogin first attempts to use the Kerberos authorization mechanism, de-
scribed below. If the remote host does not support Kerberos the standard
Berkeley rhosts authorization mechanism is used.
The options are as follows:
-8 The -8 option allows an eight-bit input data path at all times;
otherwise parity bits are stripped except when the remote side's
stop and start characters are other than ^S/^Q .
-E The -E option stops any character from being recognized as an es-
cape character. When used with the -8 option, this provides a
completely transparent connection.
-K The -K option turns off all Kerberos authentication.
-L The -L option allows the rlogin session to be run in ``litout''
(see tty(4)) mode.
-d The -d option turns on socket debugging (see setsockopt(2)) on
the TCP sockets used for communication with the remote host.
-e char
The -e option allows user specification of the escape character,
which is `~' by default. This specification may be as a literal
character, or as an octal value in the form \nnn.
-k realm
The -k option requests rlogin to obtain tickets for the remote
host in realm realm instead of the remote host's realm as deter-
mined by krb_realmofhost(3).
-l username
The -l option specifies a different username for the remote lo-
gin. If this option is not specified, your local username will
be used.
A line of the form ``<escape char>.'' disconnects from the remote host.
Similarly, the line ``<escape char>^Z'' will suspend the rlogin session,
and ``<escape char><delayed-suspend char>'' suspends the send portion of
the rlogin, but allows output from the remote system. By default, the
tilde (`~') character is the escape character, and normally control-Y
(`^Y') is the delayed-suspend character.
All echoing takes place at the remote site, so that (except for delays)
the rlogin is transparent. Flow control via ^S/^Q and flushing of input
and output on interrupts are handled properly.
KERBEROS AUTHENTICATION
Each user may have a private authorization list in the file .klogin in
their home directory. Each line in this file should contain a Kerberos
principal name of the form principal.instance@realm. If the originating
user is authenticated to one of the principals named in .klogin, access
is granted to the account. The principal accountname.@localrealm is
granted access if there is no .klogin file. Otherwise a login and pass-
word will be prompted for on the remote machine as in login(1). To avoid
certain security problems, the .klogin file must be owned by the remote
user.
If Kerberos authentication fails, a warning message is printed and the
standard Berkeley rlogin is used instead.
ENVIRONMENT
TERM Determines the user's terminal type.
SEE ALSO
rsh(1), kerberos(3), krb_realmofhost(3), krb_sendauth(3)
HISTORY
The rlogin command appeared in 4.2BSD.
BUGS
rlogin will be replaced by telnet(1) in the near future.
More of the environment should be propagated.
rlogin does not currently support encryption of the datastream when Ker-
beros authentication is used.
OpenBSD 3.0 June 6, 1993 2