Bug 89759 - "User last changed password" has the wrong date
Summary: "User last changed password" has the wrong date
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-users (Show other bugs)
(Show other bugs)
Version: 9
Hardware: All Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-27 19:30 UTC by Stefan Lasiewski
Modified: 2007-04-18 16:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-07-23 21:22:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Stefan Lasiewski 2003-04-27 19:30:12 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207

Description of problem:
I created a brand new user today (Sun Apr 27 12:23:09 PDT 2003
), but under "User Properties: Password Info", it says:

"User last changed password on: Sat Apr 26 2003" , which was yesterday. This is
incorrect. I last change the password today (Sun Apr 27 2003).

If I look for my user with the /etc/shadow file, I see the following:

# grep foo /etc/shadow

The third field says "12169", which is "Days since Jan 1, 1970 that password was
last changed" according to the man page (man 5 shadow).

Jan 1, 1970 + 12169 days = Sun Apr 27, 2003 (today).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run redhat-config-users
2. Click "Add user" and add a new user
3. Hit "Ok"
4. Select user, hit the "Properties" button
5. Click on the "Password Info" tab
6. Look and see that the box says: "User last changed password on: Sat Apr 26 2003"


Actual Results:  I see "User last changed password on: Sat Apr 26 2003"

Expected Results:  I expected to see "User last changed password on: Sun Apr 27

Additional info:

Comment 1 Matthew Miller 2003-05-08 03:22:00 UTC
Perhaps there's a time-zone issue going on here?

Comment 2 Matthew Miller 2003-05-08 13:38:10 UTC
Yeah. Here: The epoch is Jan 1, 1970 *GMT*. On the East Coast, that's an offset
of 4 or 5 hours (stupid DST).

Say you change your password at 11 pm EDT April 26th. That's 3 am GMT, so the
value that gets written to the file should be that for the next day, 12169. On
the other side of the line, if you change it at 3 pm EDT April 27, that's 7 pm
the same day GMT, and the value that gets written is the same as the one for the
local day.

Then, when reading these values back: if you apply the local timezone (which
redhat-config-users does, since it uses Python's ctime function), passwords set
in the first part of the day (before midnight GMT -- most of the day in the
western hemisphere) are shown as having been changed the previous day.

The catch is, there's no way to tell which part of the day in which a password
was set, so if you attempt to re-compensate by adding in the timezone shift,
you'll be off the other direction for passwords set in the last hours. So that's
no good.

My suggestion: just add the string " GMT" to the date as shown.

Comment 3 Brent Fox 2003-07-23 21:22:25 UTC
I took your advice and changed it to just list the date in GMT, so it avoids the
timezone problem.  I'm not using ctime anymore.  Instead I'm using gmtime() and
running that through asctime() to get some decent formatting.

Should be fixed in redhat-config-users-1.1.12-1.  Thanks for your report.

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