HOSTS.EQUIV(5)           Series 300 Only           HOSTS.EQUIV(5)

     NAME
          hosts.equiv - list of host names equivalent to current host

     HP-UX COMPATIBILITY
          Level:    HP-UX/NON-STANDARD

          Origin:   UCB

          Remarks:  Implemented on the Series 300 only.

     DESCRIPTION
          /etc/hosts.equiv   specifies   remote   hosts   which    are
          ``equivalent''  to  the  local host.  The local host permits
          users from equivalent remote hosts to access  a  local  non-
          super-user  account  without  supplying  a  password, if the
          local account's user name matches the remote user's  account
          name.  Each line in /etc/hosts.equiv consists of an official
          host name (not an alias), a blank line, or a comment.   Host
          names  consist  of any printable characters other than white
          space, newline, or `#'.  Comments begin with a `#'.

          Each user on a local host can create a $HOME/.rhosts file to
          specify  remote user names which are equivalent to the local
          user.  The local host permits  equivalent  remote  users  to
          access   the   local  user's  account  without  requiring  a
          password.  Each line in $HOME/.rhosts consists of either

          1. An official host name  followed  by  white  space  and  a
             remote user name, or

          2. A comment.  Comments begin with a `#' .

          Note that the super-user can only access  remote  hosts  via
          $HOME/.rhosts,  not  via  /etc/hosts.equiv.   Note also that
          4.2BSD allows only one blank space between the official host
          name  and  the  remote  user  name,  while  HP-UX supports a
          superset of this by allowing multiple blanks and/or tabs.

     EXAMPLES
          1) Suppose /etc/hosts.equiv in hostA contains the line

                  hostB

             and /etc/hosts.equiv in hostB is  empty.   Then  if  user
             ``Cris''  has an account named ``chm'' on hosts hostA and
             hostB, she can rlogin  to  the  account  ``chm''  without
             being  prompted  for  a password from hostB to hostA, but
             she will be prompted for a password from hostA to hostB.

          2) /etc/hosts.equiv in hostA contains:

                  hostB

     Hewlett-Packard               - 1 -             (printed 7/16/86)

     HOSTS.EQUIV(5)           Series 300 Only           HOSTS.EQUIV(5)

                  hostC

             and /etc/hosts.equiv in hostB contains:

                  hostC

             and HostC does not have a /etc/hosts.equiv, then if  user
             ``Cris''  has  an  account  named ``chm'' on hosts hostA,
             hostB, and hostC, she can rlogin to the  account  ``chm''
             without being prompted for a password from:

                  hostA     to neither hostB nor hostC.
                  hostB     to hostA
                  hostC     to hostA or hostB.

          3) If $HOME/.rhosts in account ``chm'' on hostA contains:

                  hostB root

             then  ``root''  from  hostB  can  rlogin  without   being
             prompted for a password to the account ``chm'' in hostA.

          4) If in addition to the /etc/hosts.equiv files described in
             example 2 the following files exist:

             On hostA, in the account ``root'', .rhosts is:

                  hostB root

             On hostB, in the account ``chm'', .rhosts is:

                  hostA chm

             On hostC, in the account ``guest'', .rhosts is:

                  hostA chm

             Then, user ``Cris'' can rlogin without being prompted for
             a  password,  from  hostA to the account ``chm'' on hostB
             and to the account ``guest'' on  hostC.   Also,  ``root''
             from  hostB  can rlogin without a password to the account
             ``root'' on hostA.

     FILES
          /etc/hosts.equiv
          $HOME/.rhosts

     SEE ALSO
          rcp(1), remsh(1), rlogin(1), remshd(1M), rlogind(1M).

     WARNINGS
          For security  purposes,  the  /etc/hosts.equiv  and  .rhosts

     Hewlett-Packard               - 2 -             (printed 7/16/86)

     HOSTS.EQUIV(5)           Series 300 Only           HOSTS.EQUIV(5)

          files should exist, and be readable and writable only by the
          owner, even if they are empty.

     Hewlett-Packard               - 3 -             (printed 7/16/86)