Hello, On Mon, Apr 27, 2009 at 02:42:43AM +0200, [email protected] wrote: > Nicolas François wrote: > > > This will require the same quirks. > > > > Pam is just simply not ready to receive the password at any time. The > > password might just be dropped from stdin before it even tries to read it. > > > > A conversation function is needed to communicate with PAM. > > Stdin conversation function from passwd-0.76-2.fc11.src.rpm below:
Providing a conversation function is not an issue (although there might be some uncertainties, as how it should behave if a module explicitly requested PAM_PROMPT_ECHO_ON). 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? 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). Best Regards, -- Nekral -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
