Many thanks to everyone who responded. Most people pointed me so patch
100201-04, which put me on the right track.
My final solution was to add the AUpwdauthd and AUyppasswdd pseudo-users
to /etc/passwd and /etc/security/passwd.adjunct, as instructed in the patch,
and replace the 4.1.2 version of rpc.yppasswdd with the 4.1.1 version from
the patch. Additionally, I had to add the two pseudo-users to the NIS
passwd and passwd.adjunct maps (the patch neglected to mention this vital
step :-( ).
Thank-yous and Hoorays:
-----------------------
pjy@merlin.anu.edu.au (Peter Young)
kwthomas@nsslsun.nssl.uoknor.edu (Kevin W. Thomas)
David_Boyd@imd.sterling.com (David Boyd)
Steve Riley <pacacc!steve@sacto.West.Sun.COM>
Upkar Singh Kohli <upkar@wsu-eng.eng.wayne.edu>
"(Alain Brossard EPFL-SIC/SII)" <brossard@sasun1.epfl.ch>
xcea@uxa.ecn.bgu.edu (Chad Adams)
Richard Elling <Richard.Elling@eng.auburn.edu>
xcea@uxa.ecn.bgu.edu (Chad Adams)
Original Question:
----- Begin Included Message -----
I've installed SunOS 4.1.2 on an IPC (running C2 security) which is
currently set up as an NIS master serving only itself (it'll be
serving others RSN). After bringing it up the first time it wouldn't
let anyone but root login and it complained with the following:
pwdauth: pseudo-user AUpwdauthd not found in passwd or passwd.adjunct
Upon the advice of a fellow administrator, I added the following two
lines to /etc/passwd and /etc/security/passwd.adjunct, respectively:
AUpwdauthd:##AUpwdauthd:10:10::/dev/null:/bin/sync
AUpwdauthd:*:::::
Incidentally, rpc.yppasswdd is being run from rc.local as follows
(the DIR for "-m passwd.adjunct" is defined in the /var/yp/Makefile):
rpc.yppasswdd /var/yp/etc/passwd /var/yp/etc/security/passwd.adjunct -m \ passwd.adjunct > /dev/console
After making these changes, it will let everyone login, but any attempt
to change an NIS password returns the following message (spidle2 is
the hostname):
Error from spidle2: Password incorrect
This same configuration has worked fine for quite some time now on
another master server running 4.1 (different domain). Has something
changed besides the additon of AUpwdauthd? Has anyone else experienced
this problem? I'd check the FMs, but I don't have any for 4.1.2.
----- End Included Message -----
-- Jonathan C. Davis Manager, Network Support Auburn University Alabama Cooperative Extension Service jdavis@acenet.auburn.edu 205-844-9660
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:36 CDT