Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ hosts.equiv(5N) — UTek W2.3

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

rcp(1n)

rlogin(1n)

rsh(1n)

rcmd(3n)



HOSTS.EQUIV(5N)         COMMAND REFERENCE         HOSTS.EQUIV(5N)



NAME
     hosts.equiv, .rhosts - control remote access for rsh, rcp,
     rlogin and rcmd.

DESCRIPTION
     The files /etc/hosts.equiv and .rhosts determine which users
     on which hosts may access the local file system.  System
     utilities like rlogin(1n), rsh(1n), and rcp(1n) use these
     files.

     Access is based on user login names.  Therefore it is
     important from a security standpoint that all hosts allowed
     access to the local file system are under the same
     administration (or at least cooperating closely) to prevent
     accidently assigning the same user login name to two
     different individuals.

     The file /etc/hosts.equiv is meant to be used by system
     administrators to govern which other hosts are allowed
     access to the local file system.  Typically only hostnames
     are specified in this file.  Any remote access attempt from
     any remote user (except root) on a host named in
     /etc/hosts.equiv will be permitted assuming 1) the remote
     user has an account on the local machine, and 2) the
     permissions for the local account allow accessing the target
     file.  It is also possible to limit access to a particular
     user on a particular host by specifying the username after
     the hostname.  An example hosts.equiv file follows:
        host1
        host2


     The file .rhosts is meant to be used by individual users to
     allow access from their accounts on other remote hosts or to
     allow access by other remote users to the local user's
     account.  The file must be located in the user's home
     directory.  An example .rhosts file follows:
        host1 peter
        host2 root

     In other words, remote accesses from peter on host1 will be
     allowed.  If this example .rhosts file appeared in user
     scarlett's home directory, then requests from peter on host1
     will execute on the local system as if submitted by
     scarlett.  The format of .rhosts is the same as for the
     hosts.equiv file but there is a slight change in
     interpretation.  If a hostname is listed but there is no
     username accompanying it, then access will only be permitted
     for a user on the remote host with the same user login name
     as the account on the local host in which the .rhosts file
     is located.  In other words, listing only a hostname in a
     .rhosts file does not allow access by every user on that



Printed 10/17/86                                                1





HOSTS.EQUIV(5N)         COMMAND REFERENCE         HOSTS.EQUIV(5N)



     remote host.

     The file is read each time access is attempted, so as soon
     as the file is modified, the latest version of that file
     will be in effect.

FILES
     /etc/hosts.equiv

     .rhosts

CAVEATS
     Other non-Tektronix systems may be far stricter about the
     format of the .rhost and hosts.equiv files, i.e. a hostname
     must begin in the first column, and the delimiter between
     the hostname and username must be a single space.

SEE ALSO
     rcp(1n), rlogin(1n), rsh(1n), rcmd(3n).




































Printed 10/17/86                                                2





































































%%index%%
na:72,116;
de:188,2758;3090,170;
fi:3260,111;
ca:3371,327;
se:3698,177;
%%index%%000000000105

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026