Bug 985572 - PATCH: don't set "date of last password change" /etc/shadow field when creating users
Summary: PATCH: don't set "date of last password change" /etc/shadow field when creati...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Vratislav Podzimek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-17 19:07 UTC by Hans de Goede
Modified: 2013-09-19 02:41 UTC (History)
8 users (show)

Fixed In Version: anaconda-20.17-1.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 02:41:29 UTC
Type: Bug


Attachments (Terms of Use)
anaconda users.py patch (1.04 KB, patch)
2013-07-17 19:07 UTC, Hans de Goede
no flags Details | Diff

Description Hans de Goede 2013-07-17 19:07:09 UTC
Created attachment 774935 [details]
anaconda users.py patch

Description of problem:

anaconda uses libuser, which always set the  "date of last password change" /etc/shadow field, even when password aging is not enabled (which it is not by default on Fedora, and it cannot be enabled at install time AFAIK).

This leads to a slightly inconsistent /etc/shadow, which by itself is not a big problem, where it not for bug 985569, which forces users to have to change their password immediately on first login, despite the user having been created seconds ago by initial-setup.

Attached is a patch for anacond which makes anaconda tell libuser to not set the "date of last password change" /etc/shadow field, thus leading to /etc/shadow entries which are consistent with what other tools create, and working around the libuser bug.

Comment 1 Paul Whalen 2013-08-29 15:01:00 UTC
This issue is also forcing password changes on the F20 Alpha TC2 for ARM, has this patch been considered further?

Comment 2 Vratislav Podzimek 2013-09-06 13:47:30 UTC
Patch posted to anaconda-patches. Hans, feel free to do it on your own next time.

Comment 3 Fedora Update System 2013-09-10 00:11:33 UTC
anaconda-20.13-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.13-1.fc20

Comment 4 Fedora Update System 2013-09-10 16:24:44 UTC
Package anaconda-20.13-1.fc20:
* 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.13-1.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-16296/anaconda-20.13-1.fc20
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-09-10 19:48:50 UTC
anaconda-20.14-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.14-1.fc20

Comment 6 Fedora Update System 2013-09-12 01:03:51 UTC
anaconda-20.15-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.15-1.fc20

Comment 7 Fedora Update System 2013-09-14 01:05:35 UTC
anaconda-20.16-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.16-1.fc20

Comment 8 Fedora End Of Life 2013-09-16 17:08:38 UTC
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:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 9 Fedora Update System 2013-09-16 17:48:41 UTC
anaconda-20.17-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/anaconda-20.17-1.fc20

Comment 10 Paul Whalen 2013-09-16 19:11:05 UTC
verified with anaconda-20.17-1.fc20

Comment 11 Fedora Update System 2013-09-19 02:41:29 UTC
anaconda-20.17-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.