RFC 1258 (rfc1258) - Page 1 of 5

BSD Rlogin

Network Working Group                                          B. Kantor
Request for Comments: 1258                      Univ. of Calif San Diego
                                                          September 1991


                               BSD Rlogin

Status of this Memo

   This memo documents an existing protocol and common implementation
   that is extensively used on the Internet.  This memo provides
   information for the Internet community.  It does not specify an
   Internet standard.  Distribution of this memo is unlimited.

Protocol Description

   The rlogin facility provides a remote-echoed, locally flow-controlled
   virtual terminal with proper flushing of output.  It is widely used
   between Unix hosts because it provides transport of more of the Unix
   terminal environment semantics than does the Telnet protocol, and
   because on many Unix hosts it can be configured not to require user
   entry of passwords when connections originate from trusted hosts.

   The rlogin protocol requires the use of the TCP.  The contact port is
   513.  An eight-bit transparent stream is assumed.

Connection Establishment

   Upon connection establishment, the client sends four null-terminated
   strings to the server.  The first is an empty string (i.e., it
   consists solely of a single zero byte), followed by three non-null
   strings: the client username, the server username, and the terminal
   type and speed.  More explicitly:

        
        client-user-name
        server-user-name
        terminal-type/speed

        For example:

        
        bostic
        kbostic
        vt100/9600

   The server returns a zero byte to indicate that it has received these
   strings and is now in data transfer mode.  Window size negotiation



Kantor