It's not a problem and I already ran pwconv just for the heck of it... there's only one real user, it's a suse test machine. Until I am sure exactly what it's up to in every corner I am not bothering to put anything major in it... Well how do I convert to MD5 and stay there? Even the documentation for Suse 8, I think it's from a previous version, stuff just doesn't always add up. On 2002.09.30 18:14 Christopher Mahmood wrote:
* Susan Buczak (sbuczak2@comcast.net) [020930 15:02]:
It repeatedly still will not let me enter more than 8 characters in a new password, which is probably a good sign that MD5 is not working either.
I suppose that's a problem with yast (at least it used to be). What do your passwds look like? If it's something like
user:$1$<encrypted passwd>:... then you are using md5 passwds. Keep in mind that your users will have to change their passwds if they initial had crypt passwds.
--
-ckm
* Susan Buczak (sbuczak2@comcast.net) [020930 15:21]:
Well how do I convert to MD5 and stay there?
By adding 'md5' to the pam_pwcheck.so and pam_unix2.so lines in /etc/pam.d/passwd. It sounds like you've already done this through yast2 but it wouldn't hurt to check the file.
Even the documentation for Suse 8, I think it's from a previous version, stuff just doesn't always add up.
Yes, parts of the manual are sometimes out of sync with the system; the yast stuff is often the last to be finished before the release and the manual has to be sent to published before that. -- -ckm
participants (2)
-
Christopher Mahmood -
Susan Buczak