On Wed, 2002-12-04 at 23:31, Aly S.P Dharshi wrote:
>       I don't know if the passwd program is the solution I frankly don't know
> if it would work although its worth a try, instead this works pretty
> well.
> 
> ldappasswd -s <newpassword> -D
> "uid=<loginname>,ou=People,dc=subdomain,dc=domain,dc=ca"
> -w <oldpassword> -x -h <your ldap server if not localhost>
...
> need some too for the users maybe someone can write one in say C when
> they have time (hint hint) :=)

Why?  PAM's *JOB* is to handle varied authentication back-ends
appropriately, without specific code for each one.  That's the whole
reason it exists.  You're suggesting that users ignore PAM, and stick
with the "bad old days" when interfaces weren't shared.

"passwd" remains the correct answer.  Users should never have to care
where their passwords are stored in order to set them correctly.




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to