Greetings,

A friend of mine has a box that was running "some old version of linux", at his work on a box that literally has been up for ~ 3 years. The box does pop mail & samba. The hard drive finally died a couple days ago. He replaced the hard drive and installed RedHat 6.2 then copied the password file from a tape backup overwriting the passwd file that was installed by the clean install of 6.2.

After alittle cleanup pop and samba seemed happy again.

That is, except for 3 of the 25 or 30 users, they can't pop in. It looks like its not using shadow. If we edit the password field with vipw and replace the current password for user 'bob' with the encrypted password string for that user from the tape backup copy of passwd it doesn't take, still shows "x" as the password field.

We also tried adding new users via adduser, that works without error but the checking the password field for the newly added user shows it is is 'x' (seems like it should be the encrypted salt if i am not using shadow?) and the account cant be used. Deleting a user and re-adding the user gives the same result, as does adding a new user.

I've tried going back and forth with pwconv and pwunconv and that seems to work without errors, but the password field for those three users is 'x' instead of the salted string after a pwunconv

Is there some other hidden file that is involved? Or perhaps something in the 6.2 pam config i need to change?

There is a /etc/shadow- file, can I just delete this and that will solve the problem?

As a last resort I am thinking about replacing the password file with the 6.2 default, then doing an update install to rh 7. Then pwunconv the passwd file, then appending the 30 pop users to the /etc/passwd file, then pwconv. I'd like to avoid this if possible.

I'm stumped!

Any and all suggestions greatly appreaciated!!

-joe
[EMAIL PROTECTED]
********************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the following text in the *body* (*not* the subject line) of the letter: unsubscribe gnhlug **********************************************************

Reply via email to