Bug 741552

Summary:	Password change fails
Product:	Red Hat Enterprise Linux 6	Reporter:	Diego Fernández Durán <diego>
Component:	cracklib	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	dpal
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-17 15:40:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Diego Fernández Durán 2011-09-27 09:18:48 UTC

Description of problem:
passwd fails with error.
/usr/share/cracklib/pw_dict: error reading header

Version-Release number of selected component (if applicable):
Name        : passwd
Arch        : x86_64
Version     : 0.77
Release     : 4.el6

How reproducible:
Just change a user password with passwd or system-config-users

Steps to Reproduce:
1. $ passwd
2. Write password the first time.
3. Error!
  
Actual results:
Password not set and message:

/usr/share/cracklib/pw_dict: error reading header

Expected results:
Password change.

Additional info:
The problem seems to be cracklib-dict.
The workaround found is reinstalling cracklib-dicts.

# rpm -e cracklib-dicts --nodeps
# yum install cracklib-dicts

Comment 2 RHEL Program Management 2011-09-27 09:38:46 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Nalin Dahyabhai 2011-09-27 16:42:06 UTC

I'm reasonably sure that this isn't a 32/64-bit problem, as we fixed that bug some time ago, and a spot-check shows that my 64-bit libraries don't have an issue with the files from the 32-bit version of the cracklib-dicts package.

If you can still reproduce this error, can you paste the output of these commands?

  rpm -qa --qf '%{n}-%{v}-%{r}.%{arch}\n' 'cracklib*'
  rpm -Va 'cracklib*'
  fixfiles -R passwd,pam,cracklib,cracklib-dicts check

The first will list all of the cracklib-related packages you have installed, the second will verify that their contents haven't been unexpectedly modified (and should produce no output, indicating that everything's fine), and the third will check for labeling errors on files provided by the four packages listed (its output will also be empty if there are no errors).  None of them will modify your system.

Comment 4 Nalin Dahyabhai 2011-11-29 21:31:55 UTC

Any information?

Comment 5 RHEL Program Management 2012-09-07 05:31:44 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 6 Nalin Dahyabhai 2012-12-14 21:50:34 UTC

Any information?  If not, I'm going to have to mark this as closed due to insufficient data.

Comment 7 Diego Fernández Durán 2012-12-17 08:43:03 UTC

I don't admin new systems running 6.1 anymore, so I can't test if this bug is still happening in new installed machines.

Comment 8 Nalin Dahyabhai 2012-12-17 15:40:16 UTC

Alright then.  I'm sorry we couldn't figure out what was going on here.  Marking as closed with reason insufficient-data.  If you ever run across this again, please reopen the bug.  Thanks!