sf dating service - Error updating the password file
rpc.yppasswdd will use this files, not /etc/passwd and /etc/shadow.
Shadow support in rpc.yppasswdd does not mean that it offers a very clever solution to this problem, it simply means that it can read and write password entries in the system's shadow file.
You have to produce a shadow.byname NIS map to distribute password information to your NIS clients.
If no such Makefile is found, the scripts uses the generic one in /var/yp.
The following options are available: The passwd and shadow files are located under the specified directory path.
If the user specified does not exist, or if the password, UID or GID doesn't match the information in the password file, the update request is rejected, and an error returned to the client.
If this version of the server is compiled with the CHECKROOT=1 option, the password given is also checked against the systems root password.
The password passed to the client will be in UNIX crypt() format.
rpc.yppasswdd logs all password update requests to syslogd(8)'s auth facility.
rpc.yppasswdd will search at first in the /etc/passwd file for the user and password.
If it find's the user, but the password is "x" and a /etc/shadow file exists, it will update the password in the shadow map.
The logging information includes the originating host's IP address and the user name and UID contained in the request. Unless I've screwed up completely (as I did with versions prior to version 0.5), rpc.yppasswdd should be as secure or insecure as any program relying on simple password authentication. You can use and distribute it under the GNU General Public License Version 2.