|Product:||[Retired] Red Hat Linux||Reporter:||carl.williams|
|Component:||ypserv||Assignee:||Cristian Gafton <gafton>|
|Status:||CLOSED NEXTRELEASE||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||1999-09-14 23:20:51 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description carl.williams 1999-09-01 18:24:06 UTC
In the "so-called resolved bug report 3126" several people have mentioned that rpc.yppasswd dies when a NIS user tries to change his passwd. This problem is even more severe if the user is running shadow passwords. Although the passwd file gets updated and thus restarting the yppasswd daemon allows the next user to crash the daemon -- if you are running shadow passwords the shadow file DOES NOT get updated. Thus the previous passwd is only changed on the NIS server and his old passwd remains on all NIS clients. I can only get around this problem by recreating the whole yellow pages map. Is there a solution that is less painful? In reality this is close to being a security risk since the old password remains viable on all cluster members -- and thus compromised passwords remain unchanged.
Comment 1 Jeff Johnson 1999-09-08 16:36:59 UTC
Does this problem still exists in the latest yp packages from Raw Hide. AFAICT, the latest packages are yp-tools-2.3-2.i386.rpm ypbind-3.3-23.i386.rpm ypserv-1.3.7-3.i386.rpm ------- Additional Comments From 09/14/99 14:37 ------- yes, ypserv-1.3.7-3 from rawhide works. Should probably be in updates ...