DataMuseum.dk

Presents historical artifacts from the history of:

Rational R1000/400 Tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Rational R1000/400 Tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download
Index: ┃ R T

⟦5d7af1df6⟧ TextFile

    Length: 5501 (0x157d)
    Types: TextFile
    Names: »RSHD_DOC«

Derivation

└─⟦5f3412b64⟧ Bits:30000745 8mm tape, Rational 1000, ENVIRONMENT 12_6_5 TOOLS 
    └─ ⟦91c658230⟧ »DATA« 
        └─⟦458657fb6⟧ 
            └─⟦a5bbbb819⟧ 
                └─⟦this⟧ 
└─⟦8ee07855d⟧ Bits:30000545 8mm tape, Rational 1000, DTIA 2_1_6
    └─ ⟦0c25cb74a⟧ »DATA« 
        └─⟦0182c9918⟧ 
            └─⟦ed024cadb⟧ 
└─⟦d0624311f⟧ Bits:30000529 8mm tape, Rational 1000, DTIA 2_1_7
    └─ ⟦f494b5154⟧ »DATA« 
        └─⟦3ddce7122⟧ 
            └─⟦ed024cadb⟧ 
                └─⟦this⟧ 
└─⟦d10a02448⟧ Bits:30000409 8mm tape, Rational 1000, ENVIRONMENT, D_12_7_3
    └─ ⟦fc9b38f02⟧ »DATA« 
        └─⟦9b46a407a⟧ 
            └─⟦eec0a994f⟧ 
                └─⟦this⟧ 

TextFile




RSHD(8C)              MAINTENANCE COMMANDS               RSHD(8C)



NAME
     rshd - remote shell server

SYNOPSIS
     /etc/in.rshd host.port

DESCRIPTION
     _▶08◀R_▶08◀s_▶08◀h_▶08◀d is the server for  the  _▶08◀r_▶08◀c_▶08◀m_▶08◀d(3N)  routine  and,  conse-
     quently,  for  the  _▶08◀r_▶08◀s_▶08◀h(1C)  program.   The  server provides
     remote execution facilities  with  authentication  based  on
     privileged port numbers.

     _▶08◀R_▶08◀s_▶08◀h_▶08◀d is invoked by _▶08◀i_▶08◀n_▶08◀e_▶08◀t_▶08◀d(8C) each time a  shell  service  is
     requested, and executes the following protocol:

     1)   The server checks the client's  source  port.   If  the
          port  is not in the range 0-1023, the server aborts the
          connection.  The clients host address (in hex) and port
          number (in decimal) are the argument passed to _▶08◀r_▶08◀s_▶08◀h_▶08◀d.

     2)   The server reads characters from the  socket  up  to  a
          null  (`\0') byte.  The resultant string is interpreted
          as an ASCII number, base 10.

     3)   If the number received in step 1  is  non-zero,  it  is
          interpreted as the port number of a secondary stream to
          be used for the stderr.  A second  connection  is  then
          created  to the specified port on the client's machine.
          The source port of this second connection  is  also  in
          the range 0-1023.

     4)   The server checks the client's source address.  If  the
          address   is  associated  with  a  host  for  which  no
          corresponding entry exists in the host name  data  base
          (see _▶08◀h_▶08◀o_▶08◀s_▶08◀t_▶08◀s(5)), the server aborts the connection.

     5)   A null terminated user name of at most 16 characters is
          retrieved  on  the  initial  socket.  This user name is
          interpreted as a user identity to use on  the  server's
          machine.

     6)   A null terminated user name of at most 16 characters is
          retrieved  on  the  initial  socket.  This user name is
          interpreted  as  the  user  identity  on  the  client's
          machine.

     7)   A null terminated command to be passed to  a  shell  is
          retrieved  on  the  initial  socket.  The length of the
          command is limited by the upper bound on  the  size  of
          the system's argument list.

     8)   _▶08◀R_▶08◀s_▶08◀h_▶08◀d then validates the user according to the following



Sun Release 3.5    Last change: 3 January 1984                  1






RSHD(8C)              MAINTENANCE COMMANDS               RSHD(8C)



          steps.   The remote user name is looked up in the pass-
          word file and a _▶08◀c_▶08◀h_▶08◀d_▶08◀i_▶08◀r is performed to the  user's  home
          directory.   If  the lookup or fails, the connection is
          terminated.  If the _▶08◀c_▶08◀h_▶08◀d_▶08◀i_▶08◀r fails, it does a _▶08◀c_▶08◀h_▶08◀d_▶08◀i_▶08◀r  _▶08◀t_▶08◀o  /
          (root).   If  the  user is not the super-user, (user id
          0), the file /_▶08◀e_▶08◀t_▶08◀c/_▶08◀h_▶08◀o_▶08◀s_▶08◀t_▶08◀s._▶08◀e_▶08◀q_▶08◀u_▶08◀i_▶08◀v is consulted for  a  list
          of  hosts  considered  ``equivalent''.  If the client's
          host name is present in this file,  the  authentication
          is  considered successful.  If the lookup fails, or the
          user is the super-user, then the file  ._▶08◀r_▶08◀h_▶08◀o_▶08◀s_▶08◀t_▶08◀s  in  the
          home  directory  of  the remote user is checked for the
          machine name and identity of the user on  the  client's
          machine.   If this lookup fails, the connection is ter-
          minated.

     9)   A null byte is returned on  the  connection  associated
          with  the  stderr and the command line is passed to the
          normal login shell of the user.  The shell inherits the
          network connections established by _▶08◀r_▶08◀s_▶08◀h_▶08◀d.

DIAGNOSTICS
     All diagnostic messages are returned on the connection asso-
     ciated  with the stderr, after which any network connections
     are closed.  An error is indicated by a leading byte with  a
     value  of  1  (0 is returned in step 9 above upon successful
     completion of all the steps prior to the command execution).

     ``locuser too long''
     The name of the user on the client's machine is longer  than
     16 characters.

     ``remuser too long''
     The name of the user on the remote machine is longer than 16
     characters.

     ``command too long ''
     The command line passed exceeds the  size  of  the  argument
     list (as configured into the system).

     ``Hostname for your address unknown.''
     No entry in the host name database existed for the  client's
     machine.

     ``Login incorrect.''
     No password file entry for the user name existed.

     ``Permission denied.''
     The authentication procedure described above failed.

     ``Can't make pipe.''
     The pipe needed for the stderr, wasn't created.




Sun Release 3.5    Last change: 3 January 1984                  2






RSHD(8C)              MAINTENANCE COMMANDS               RSHD(8C)



     ``Try again.''
     A _▶08◀f_▶08◀o_▶08◀r_▶08◀k by the server failed.

     ``/bin/sh: ...''
     The user's login shell could not be started.

SEE ALSO
     rsh(1C), rcmd(3N)

BUGS
     The authentication procedure used here assumes the integrity
     of  each  client machine and the connecting medium.  This is
     insecure, but is useful in an ``open'' environment.

     A facility to allow  all  data  exchanges  to  be  encrypted
     should be present.







































Sun Release 3.5    Last change: 3 January 1984                  3