Ian Mortimer wrote: > Configure the clients to use md5 passwords using authconfig. The next > users changes their password the passwd command will md5 encrypt it. > Once all the users have changed their passwords you'll have all md5 > passwords. If you configure the server to generate md5 passwords, > yppasswd will work the same.
I ran authconfig --enablemd5 --update on the yp server and restarted yppasswd. Running "yppasswd testusr" as root (on the server) didn't update the password with a MD5 password in the NIS password file, but put in a normal DES password. Adding MD5 passwords by hand into the NIS password source seems to work, but I can't persuade yppasswd to update the NIS database with a MD5 password. Maybe it's time to look into LDAP (if I get a spare few weeks...)... Jeremy -- Jeremy Sanders <[EMAIL PROTECTED]> http://www-xray.ast.cam.ac.uk/~jss/ X-Ray Group, Institute of Astronomy, University of Cambridge, UK. Public Key Server PGP Key ID: E1AAE053 _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
