Sun Microsystems Sun Workstation 100U System Manager's Manual page 98

SUD
100/150 Installation Manual System Set-Up and Operation
remote processes. Of course, if he can rlogin he can always doctor his .rhod, file (if you have
given him a home directory). This brings up two points:
1.
The only way to achieve anything resembling security in a hostile environment is to exclude
users from the / etc/ pa"wd file; once someone knows a password, he's in. If this concerns
-you, you should also be especially careful to protect / .rho,t, properly - make sure it is
writable only by root. Clearly, tight security has not really been an issue in the administra-
tion of previous
UNIX
systems; the goal has been to facilitate, rather than deny, access.
2. If you are dealing with a more open environment, the easiest way to administer machine
access at the user level is to give each 'trusted' user an account (in / etc/ pa"wcl) and a home
directory on your machine{s), and ask each user to create his/her own .rho,t, file in his/her
home directory on the machine{s).
6.1.4.
Making
1.1
Networks Compatible with Existing Networks
The shift in network addressing format in Release 1.1 should only be a concern for you if
• You have a network of machines running version 1.0 (or lower) of Sun software, and you
want them to communicate with your new workstation{s} running 1.1, or
• You have a machine which cannot perform ARP (an older VAX, for example), and you want
it to talk to your 1.1 Sun's.
If neither of these is the case, don't worry about it.
To make machines running 1.1 talk to 1.0 networks or machines which do not respond to or
perform ARP, you can do one of three things:
1. The best path is to convert your 1.0 network to the Class C addressing scheme described in
the previous section. If this is impossible in your system -
for example, if you have older
Vaxen that cannot perform ARP (some 4.1c machines) - then try solution 3. Otherwise,
we urge you to convert.
This is easier than it sounds. You'll need to assign your old network a new network number
(use "192.200.1" if you wish); assign each machine on the old network a new, unique host
number between 1 and 254; and, finally, edit the / etc/ hod' file and change your old network
number to your new network number, and identify each host with its host number. For
example, if my'()ld
/etc/ho~t,
file looked like this:
125.5143 alpha-.
125.5204 beta
125.6422 gamma
125.0x5245 delta
125.0x2226
epsilon
My new one might look like this:
192.9.200.1 alpha
192.9.200.2 beta
192.9.200.3 gamma
192.9.200.4 delta
192.9.200.5 epsilon
In the example above, "192.9.200" is the network number, and "1" is alpha's host number.
Then, install /
ftC/
hod' on all systems. Finally, reboot any machine whose host number you
have changed.
Revision H of 12 March 1984
6-5