Dear wise ones,
I've been battling with Enhanced Security and NIS under OSF/1
v3.0 (OSFBASE301 and OSFC2SEC301 from the complementary CD
are also installed) on a 2100. It strikes me as being pretty
unusable but perhaps I've done something wrong or have missed
a vital piece of explanatory documentation (is there anything
to refer to besides the v3.0 Security manual?).
What are other people's experiences?
In particular, the following are the most obvious problems
I'm trying to work around. I would be interested to know if
we're the only ones suffering, or if there are fixes.
1) Every NIS client seems to need its own /tcb tree and
associated auth files. I don't see how these are meant
to be propagated from the NIS master.
2) XIsso gives you a full pick list of users, but when you
select a NIS-registered user it brings the error 'The
User Name cannot be found'. It only works if /etc/passwd
and /var/yp/src/passwd are one and the same, which can be
done with links but it is not a desirable configuration.
3) Even if you use links to sort out the XIsso problem on
the NIS master, XIsso still doesn't work on a NIS slave
or client. This means that blocked users have to be
unblocked by manually editing the appropriate auth file.
4) When I use XSysAdmin to create a new user in the network
maps on the NIS master it core dumps. It seems to do the
job though, except it doesn't update the 'extended
profile' map prpasswd.
I have a few other gripes as well, like you use the XSysAdmin
user to create an account but then have to go to the XIsso
utility to unblock it... and the GUIs don't let you set a
user's password... and parent/child windows sometimes lose
'current' context, but these problems are not directly
related to NIS.
Is there anybody out there using Enhanced Security and NIS
who is actually happy with it?
Regards,
Jon Buchanan, Zuerich, Switzerland
[ Jonathan.Buchanan_at_cs.csh.com ]
Received on Tue Jan 03 1995 - 09:35:22 NZDT