Bug 231062

Summary: [LSPP] cupsd is unable to increment pam_tally2's tallylog
Product: Red Hat Enterprise Linux 5 Reporter: Matt Anderson <mra>
Component: selinux-policyAssignee: Daniel Walsh <dwalsh>
Status: CLOSED ERRATA QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: ebenes, iboverma, krisw, linda.knippers, sgrubb
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHBA-2007-0544 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-07 16:38:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 224041    

Description Matt Anderson 2007-03-05 21:35:08 UTC
Description of problem:
cupsd is not allowed to increment the faillog when a user enters a wrong password.

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

How reproducible:

Steps to Reproduce:
1. Ensure that pam_tally2.so is required for auth in /etc/pam.d/cups
2. Use `lprm -U bob 42` to cancel a job
3. Enter a bad password when prompted for bob's password
Actual results:
User's account is not locked.

Expected results:
Once the maximum number of invalid attempts are met, the account needs to be locked.

Additional info:
allow cupsd_t faillog_t:file { append getattr read write };

Comment 1 Matt Anderson 2007-03-05 21:38:11 UTC
fix the summary title

Comment 2 Daniel Walsh 2007-03-06 18:22:17 UTC
Fixed in selinux-policy-2.5.6-43

Comment 7 errata-xmlrpc 2007-11-07 16:38:33 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.