Copyright (c) 1983, 1990 The Regents of the University of California.
All rights reserved.

%sccs.include.redist.man%

@(#)rlogin.1 6.15 (Berkeley) 06/24/90

C 5 rlogin - remote login rlogin [ -8KLdx ] [ -e char ] [ -k realm ] [ -l username ] host Rlogin starts a terminal session on a remote host host .

Rlogin first attempts to use the Kerberos authorization mechanism, described below. If the remote host does not supporting 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. Eight-bit mode is the default.

-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 By default, the tilde (``~'') character is the escape character. The -e option allows specification of a different escape character.

-k The -k option requests rlogin to obtain tickets for the remote host in realm realm instead of the remote host's realm as determined by krb_realmofhost (3).

-x The -x option turns on DES encryption for all data passed via the rlogin session. This may impact response time and CPU utilization, but provides increased security.

A line of the form ``~.'' disconnects from the remote host, where ``~'' is the escape character. Similarly, the line ``~^Z'' will suspend the rlogin session. Substitution of the delayed-suspend character (normally ^Y) for the suspend character suspends the send portion of the rlogin, but allows output from the remote system.

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.

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 password 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.

rsh(1), kerberos(3), krb_sendauth(3), krb_realmofhost(3) Rlogin will be replaced by telnet (1) in the near future.

More of the environment should be propagated.