Bug 231062 - [LSPP] cupsd is unable to increment pam_tally2's tallylog
[LSPP] cupsd is unable to increment pam_tally2's tallylog
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: selinux-policy (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
Depends On:
Blocks: RHEL5LSPPCertTracker
  Show dependency treegraph
Reported: 2007-03-05 16:35 EST by Matt Anderson
Modified: 2007-11-30 17:07 EST (History)
5 users (show)

See Also:
Fixed In Version: RHBA-2007-0544
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 11:38:33 EST
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 Matt Anderson 2007-03-05 16:35:08 EST
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 16:38:11 EST
fix the summary title
Comment 2 Daniel Walsh 2007-03-06 13:22:17 EST
Fixed in selinux-policy-2.5.6-43
Comment 7 errata-xmlrpc 2007-11-07 11:38:33 EST
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.


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