Nicolas François wrote: > My point was that the same conversation function can be used for chpasswd, > newusers, and passwd (i.e. I did not agree to "...but instead of all the > quirks to get the encrypted password back from pam...") > > Once chpasswd supports PAM, do you still need passwd --stdin?
no, not at all, PAM support in chpasswd would be equally nice. But chpasswd should complain loud if it doesn't support pam. (eg. --pam where older chpasswd versions exit with error). > Supporting PAM in chpasswd looks much easier than supporting > non-interactive password updates in passwd. (mostly because of the non-PAM > paths) > >>From the documentation point of view, this would also be easier to have > different tools: > * passwd - update passwords interactively > * chpasswd - update passwords in batch mode > > So if the use case is only "To set the password from scripts.", I would > just propose to use chpasswd for this (once it will be fixed). ACK! michael
signature.asc
Description: OpenPGP digital signature
