Bug 201202 - pam_tally missing lock_time and unlock_time parameter
pam_tally missing lock_time and unlock_time parameter
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: pam (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2006-08-03 11:45 EDT by Nicolas Scheibling
Modified: 2015-01-07 19:13 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-03 12:06:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nicolas Scheibling 2006-08-03 11:45:15 EDT
Description of problem: 
The pam_tally module didn't know lock_time and unlock_time arguments 
Version-Release number of selected component (if applicable): 
RHEL 3 Update 6 
How reproducible: 
Add the two following lines into the file /etc/pam.d/system_auth  
auth        required      /lib/security/$ISA/pam_tally.so onerr=fail 
account     required      /lib/security/$ISA/pam_tally.so onerr=fail deny=3 
no_magic_root lock_time=15 unlock_time=1800 
Steps to Reproduce: 
1. Add the pam_tally configuration (see above) into 
the /etc/pam.d/system_auth/system-auth file 
2. Try to do some login with a false password. 
3. Watch the logs 
Actual results: 
The syslog displays:  
pam_tally: unknow option; unlock_time=1800 
pam_tally: unknow option; lock_time=15 
Expected results: 
User should be locked after 3 failled login, and unlocked after waiting 1800 
seconds (30 minutes) 
Additional info: 
Comment 1 Tomas Mraz 2006-08-03 12:06:06 EDT
This problem will be resolved in a future major release of Red Hat Enterprise
Linux. Red Hat does not currently plan to provide a resolution for this in a Red
Hat Enterprise Linux update for currently deployed systems.

With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects. 

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