Re: [Bug-sysutils] Non-interactive password entry

[Ben Asselstine]

setpasswd was (is) already way too big.  It's on the TODO list to
break it up into more sensible chunks.

In the meantime I don't see a problem with passing in a password to
setpasswd.  If a password is passed in then it won't ask the user for
one.

regards,

Ben

On 3/28/07, Barry deFreese <address@hidden> wrote:
> Hi folks,
>
> I was (am) looking at both mkuser taking a file as input and/or adding
> chuser (with limitations).  However, as far as I can tell, all of our
> other programs that manipulate passwords do so interactively.  Obviously
> I can fake this but with Ben's new libpasswd does it make sense to
> extend setpasswd to take password as a param or maybe create a mirror
> function that works non-interactively and accepts password as a parm?
> The other question there that I don't know the answer to is: Is there a
> security risk in doing so?  (Of course I'm not sure it could be any more
> of a risk that the passwords sitting in the input file?)
>
> Thanks!
>
> Barry deFreese (aka bddebian)
>
>
> _______________________________________________
> Bug-sysutils mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-sysutils