Shadowed passwords is not the problem of Expect. Expect just spawns the
'passwd' command which should support shadow.
The workaround with PAM featured systems in changing passwords is to
disable its checking of new passwords if it's strong or not.
Edit /etc/pam.d/passwd, (lines 3 and 4 are commented)
auth required /lib/security/pam_pwdb.so shadow nullok
account required /lib/security/pam_pwdb.so shadow
#password required /lib/security/pam_cracklib.so retry=3
#password required /lib/security/pam_pwdb.so use_authtok nullok
password required /lib/security/pam_pwdb.so
The third line comments out the library that aids the checking of stronger
passwords.
The fourth line with "use_authtok" argument ensures that the pam_pwdb
module does not prompt for a password, but instead uses the one provided by
pam_cracklib, while nullok accepts blank passwords (no passwords).
Comment out the third line and take out use_authtok and nullok
parameters (check out the fifth line). This disables PAM in sending
unexpected messages for Expect when you have weak passwords.
Check out /usr/doc/pam-0.59/html directory for more of PAM in your RH 5.0
distribution.
Btw, an '*' in the password field in /etc/passwd, if your system supports
shadow might probably mean that you're using the old version of shadow
utils check out the version of your shadow utils. RH 5.0 comes with the
newer version of shadow utils, where '*' was changed to 'x'.
On Thu, 16 Apr 1998, Rich Burroughs wrote:
> Doug,
>
> I saw this same thing on a client's box recently. I heard about it well
> after it broke so the cause is hard to pinpoint, but I believe the problem
> came up when we converted the box to use shadow passwords.
>
> When I run the expect script they had been using, the process now hangs
> after it enters the first password. When I tried autopasswd it slowed
> down after entering the password the second time, but did seem to
> complete. When I look in the shdow file I just see an asetrisk in the
> password field.
>
> Are you using shadow? Maybe we're seeing the same thing. I'm assuming
> that my problem is tied to pam/pwdb stuff, but I'm not sure what it is.
> I'm running the script as root, and when I do a passwd at the command line
> it works fine...
>
>
> Rich
>
>
>
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
