when I install a box for a user that I know will not be taken into use on a hostile network, I generally have this in my kickstarts [...] # create a user user --name=user --password=geheim [...] %post ( # # set a full name chfn -f 'test user' user # # set empty password passwd -d user # # force password change chage -d 0 user # the two steps above of course only make sense if you install in a trusted network # and then log in once to set password BEFORE you put the machine in an untrusted network. # If you can not do this, set a decent password higher up in this file and disable the -d step [...] It would be nice if anaconda's user option was able to achieve this, e.g. with a --passwordsetonfirstlogin option. The aim is that after installation the user is given the machine (which is set up to come up in run level 5) she/he can click her/his username in gdm and is then be prompted to set a password of their choice.
See also: bug 550351
anaconda-26.21.4-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f620d8c7c2
Looks like the Bodhi web UI likes to add random unrelated bugs to an update...
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.