Bug 109499 - chage -l improperly reports zero val in account expiration field
Summary: chage -l improperly reports zero val in account expiration field
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: shadow-utils
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Peter Vrabec
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-08 18:42 UTC by Brad Smith
Modified: 2007-04-18 16:59 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-04-19 09:04:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Brad Smith 2003-11-08 18:42:15 UTC
Description of problem:
If the account expiration value is set to zero, the account is set to
expire zero days after the epoch ie 01/01/70, which effectively
disables the account. However, chage -l lists values <=0 as 'Never'.

Version-Release number of selected component (if applicable):
shadow-utils-4.0.3-6

How reproducible:
Every time

Steps to Reproduce:
1.chage -l foo    //will show user foo's expire date as 'Never'
2.chage -E0 foo   
3.chage -l foo    //still 'Never'
4.su - foo        //'Account Expired' message
  
Actual results:
'chage -l' shows 'Never', even though the account is expired

Expected results:
Should show account expiration date of 01/01/1970

Additional info:
'chage -E1 foo ; chage -l foo' produces the expected results
(01/02/1970, in this case)


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