This is a good point. I don't think Samba supports pam.d rejection of
passwords and since I'll be using password synchronization this is really
important. I guess I'll just have to live with weak passwords untill a
better solution comes my way.
Has anyone tried to do something like this?
----- Original Message -----
From: "Anthony Moulen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 26, 2001 3:08 PM
Subject: Re: [expert] Password issues
> Perhaps you could remove the pam.d passwd requirement to use cracklib. I
> would suggest you make a copy first of passwd entry in the pam.d folder,
> then make your change, then try to set the password to some insecure.
>
> After you finish setting the passwords put the cracklib back in place,
> then users should be informed that you want them to reset their passwords.
>
> They should now not be able to set the password to something against the
> cracklib rules (this is assuming that the Samba integration supports
> pam.d rejecting passwords).
>
> Good luck.
>
>
>
>
