Bug 811243

Summary:	pam_cracklib: difignore is no-op in the current package - needs man page update
Product:	Red Hat Enterprise Linux 6	Reporter:	Miroslav Vadkerti <mvadkert>
Component:	pam	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED ERRATA	QA Contact:	Dalibor Pospíšil <dapospis>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.3	CC:	dapospis
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	pam-1.1.1-12.el6	Doc Type:	Bug Fix
Doc Text:	This is just man page fix, no need to mention in the errata text.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-21 10:36:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	836160

Description Miroslav Vadkerti 2012-04-10 14:10:34 UTC

Description of problem:
According to the developer the difignore option is no-op in the current implementation. This should be properly documented in the man page

Version-Release number of selected component (if applicable):
pam-1.1.1-10.el6_2.1

How reproducible:
100%

Steps to Reproduce:
1. man pam_cracklib


Actual results:
difignore is no-op but man page says something else

Expected results:
difignore properly documented that it is a no-op in current release

Additional info:
Not a regression

Comment 1 RHEL Program Management 2012-07-10 06:10:31 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 2 Ludek Smid 2012-07-11 11:41:29 UTC

This request was erroneously removed from consideration in
Red Hat Enterprise Linux 6.4, which is currently under
development.  This request will be evaluated for inclusion
in Red Hat Enterprise Linux 6.4.

Comment 11 errata-xmlrpc 2013-02-21 10:36:53 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0521.html