Red Hat Bugzilla – Bug 977732
in 19 Final text install, ordinary user password in kickstart file is unencrypted
Last modified: 2013-11-09 13:43:11 EST
Description of problem:
Doing a minimal text install from the 19 Final RC1 DVD (either i386 or x86_64), during which I set an ordinary user password, it appears in plaintext in the kickstart file. When I did a minimal GUI install in the same way, it is encrypted. A root password is always encrypted regardless of install method. This is the first compose where I looked at the kickstart file, so I don't know when this problem started.
Version-Release number of selected component (if applicable):
Reproduced. Root pw encrypted, user pw unencrypted. Text mode.
The same happens with 19 Final TC6 and with 19 Beta Gold.
This has very likely always been the case, we only started encrypting the root password specifically a few releases back after a big argument. I'm less worried about a user password, really. Anyone else particularly concerned about this?
I don't see a good reason _not_ to encrypt a password, normal user or not. It's also not exactly difficult to do. That said, I'm ok with just fixing this in master branch, not f19-branch.
Samantha: I can't find the bug for the root password offhand, and I don't exactly remember what the argument against encrypting it was.
The user password should always be encrypted, because if the user is an administrator (in group "wheel"), the user can become root by running "sudo su" and entering the user password.
Also, some people use the same password or similar passwords for the root and user accounts, so knowing one gives attackers the other. If both passwords are encrypted, the encrypted passwords will be different, so neither can be used to get the other.
Verified with F19 Final.
Thanks for catching this, Andre.
This bug should probably have the "Security" keyword.
It's pretty clearly an oversight, given that a GUI install encrypts the user password and only a text install doesn't.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.
More information and reason for this action is here:
Patch posted for review.
Patch pushed, commit 64609a7f42a762741fadef1d3ead11d231593f7f in master.
anaconda-20.20-1.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-20.20-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
anaconda-20.21-1.fc20 has been submitted as an update for Fedora 20.
After doing text installs with 20 Beta TC1 (anaconda 20.21-1) I cannot log in with my ordinary user account, even though anaconda-ks.cfg shows an encrypted user password. The root password works fine. After installation, I can use the passwd command to change the user password to the same password I chose during install, and am then able to log in.
Andre, that would probably be a blocker. Could you report it as a separate bug and propose it as a Beta blocker (put this bug number into See Also)? Thanks a lot.
After a minimal text install from the 20 Beta TC2 x86_64 DVD, both root and user passwords are encrypted, and I can log in with either account.
Closing as this works fine in 20 Beta RC5 (Gold) and anaconda-20.25.6-1 has been pushed stable.