Bug 19915

Summary:	During an upgrade from 6.0 to 7, the PAM configuration is broken
Product:	[Retired] Red Hat Linux	Reporter:	Panic <mdrew>
Component:	pam	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED ERRATA	QA Contact:	Aaron Brown <abrown>
Severity:	medium	Docs Contact:
Priority:	low
Version:	7.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-10-30 20:54:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Panic 2000-10-27 15:15:49 UTC

An upgrade from 6.0 to 7 breaks the PAM configuration, resulting in the
inability to log in after the upgrade.  6.0 is confirmed, and 6.1 is
probable.  I haven't checked 6.2 yet (and that may be a while), nor have I
researched this thoroughly.  I'll update when I get a chance.

Booting with "linux single" and re-running authconfig fixes the problem for
both of the customers that I've dealt with on this issue.

Comment 1 Nalin Dahyabhai 2000-10-30 20:54:08 UTC

Upgrades don't correctly detect if shadow passwords are disabled, and they are
enabled by default.  This does not show up on fresh installations because
authconfig is run by the installer to toggle these settings.  A test version of
the package which correctly handles this transition is at
http://people.redhat.com/nalin/test/.  Please see if it fixes the problems
you're seeing.

Comment 2 Nalin Dahyabhai 2001-02-12 20:19:50 UTC

Corrected in the errata release.