Bug 1031263

Summary:	authconfig symlinks password-auth to password-auth-ac, which collides with pam
Product:	[Fedora] Fedora	Reporter:	Ambarish Sridharanarayanan <fedora>
Component:	authconfig	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	19	CC:	awilliam, jlieskov, tmraz
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-30 08:54:08 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:

Description Ambarish Sridharanarayanan 2013-11-16 09:34:09 UTC

Description of problem:

authconfig creates /etc/pam.d/password-auth-ac and symlinks /etc/pam.d/password-auth to it. Unfortunately, the latter file is owned by pam, so if a newer pam updates /etc/pam.d/password-auth, it collides with the symlink, and ends up creating /etc/pam.d/password-auth.rpmnew.

Version-Release number of selected component (if applicable):
authconfig-6.2.6-3.fc19.1.i686
pam-1.1.6-12.fc19.i686

How reproducible:
No idea, to be honest. I found an rpmnew file, and worked backwards to figure out what could have gone wrong.

Comment 1 Tomas Mraz 2013-11-18 08:27:06 UTC

This is not a bug. It works as it is expected.

Comment 2 Adam Williamson 2013-12-04 17:38:49 UTC

Compare and contrast: https://bugzilla.redhat.com/show_bug.cgi?id=194246 ... :)

Comment 3 Ambarish Sridharanarayanan 2013-12-30 01:39:28 UTC

I disagree that this is expected. Certainly, users would find it unexpected.

a. What is a user supposed to do anyway, when they see this? Just delete the rpmnew files?
b. Aren't we losing information? What if the rpmnew file contained an update? Right now, the 2 packages are just fighting with one another, and I don't see how that can ever be The Right Thing.

Comment 4 Tomas Mraz 2013-12-30 08:54:08 UTC

I just don't see any way how to workaround this. The configuration in pam package is a default one. The configuration from authconfig is user configured.