Description of problem: pwkickstart is not usable in a non-interactive script. One use-case is a cobbler trigger (but I suppose also a foreman hook can be a good example) as you can generate a "per-system" snippet which can be embedded on the kickstart file Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. echo "mypassword" | pwkickstart 2. 3. Actual results: The program expects a password from the user Expected results: The program accept a password from the standard input Maybe, a specific switch (for example "-s" or "--stdin") can be implemented to modify the actual interactive behaviour. Additional info: It would also be great if we can pass an option to specify the encryption method instead of printing all the different methods (md5, sha-256 and sha-512). For reference, you can take a look at the "mkpasswd" included in the the debian/ubuntu whois package (https://packages.ubuntu.com/artful/whois) http://manpages.ubuntu.com/manpages/artful/en/man1/mkpasswd.1.html
Done! https://github.com/lzap/pwkickstart/commit/eacbe9f4d7dfcb90b22893c43f75e9ced3e6fbb7
pwkickstart-1.0.3-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-4c7864b3e7
pwkickstart-1.0.3-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-4c7864b3e7
pwkickstart-1.0.3-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.