My original posting:
From the man page for securenets
The netmask field may be either 255.255.255.255 or the
string ``host'' indicating that the second field is a
specific host to be allowed access.
However, when "host 192.168.164.5" is the only entry in
/var/yp/securenets, my NIS server responds not only to requests
from 192.168.164.5 but to those from other clients.
The prompt response from Robert.Tommaselli@ska.com precisely explained
what I am experiencing:
My experience with this is that I had hoped to make a machine into a
slave server that would only bind to it's self and NOT serve
nis maps to any other hosts on any subnet. I too put only one line in the
securenets file but it was "host xxx.xxx.xxx.xxx". The behavior I observed was
that any yp client that uses the -broadcast option was getting bound to the
slave server in question but no maps were being served, ie locking up
the client station by being bound but not served. I called sun and asked
for an enhancement that will not allow the ypserving machine to grant binds
but not serving maps. This totally hosed my jumpstarts until I figured
out why they were freezing after they get a nis server.
I opened a service order with Sun (SO#2566190) and was later told flat
out that the designers of NSKit had wanted it to function this way and
had no intention to change it.
Thanks also go to Peter.Bestel@uniq.com.au and firstname.lastname@example.org.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:09 CDT