Bug 758601

Summary:	/etc/pam.d/ejabberd references non-existent config password-auth
Product:	[Fedora] Fedora EPEL	Reporter:	Nikolay <themostrareword>
Component:	ejabberd	Assignee:	Peter Lemenkov <lemenkov>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	el5	CC:	jkaluza, lemenkov, martin, mmahut
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-23 20:23:47 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 Nikolay 2011-11-30 08:07:09 UTC

Description of problem:
/etc/pam.d/ejabberd configuration file includes non-existent file password-auth, making PAM configuration inconsistent.

Version-Release number of selected component (if applicable):
ejabberd-2.1.8-2.el5

How reproducible:
always

Steps to Reproduce:
1. Install ejabberd-2.1.8-2.el5.x86_64.rpm (or another one with appropriate architecture).
2. Check /etc/pam.d/ejabberd contents. You'll see that password-auth is referenced.
 $ cat /etc/pam.d/ejabberd
 #%PAM-1.0
 auth       include      password-auth
 account    include      password-auth
3. Check /etc/pam.d/password-auth file existence.
  
Actual results:
password-auth file doesn't exist, but is referenced.

Expected results:
ejabberd PAM configuration file doesn't reference non-existent files. E.g. instead of 'password-auth' it includes 'passwd' or 'system-auth'.


Additional info:

OSes:
 $ cat /etc/redhat-release
 CentOS release 5.7 (Final)
and
 $ cat /etc/redhat-release
 Red Hat Enterprise Linux Server release 5.7 (Tikanga)

Comment 1 Fedora Update System 2012-07-15 07:53:58 UTC

ejabberd-2.1.11-3.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/ejabberd-2.1.11-3.el5

Comment 2 Fedora Update System 2012-07-15 07:54:18 UTC

ejabberd-2.1.11-3.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/ejabberd-2.1.11-3.fc16

Comment 3 Fedora Update System 2012-07-15 07:54:33 UTC

ejabberd-2.1.11-3.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/ejabberd-2.1.11-3.fc17

Comment 4 Fedora Update System 2012-07-15 07:54:50 UTC

ejabberd-2.1.11-3.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/ejabberd-2.1.11-3.el6

Comment 5 Fedora Update System 2012-07-15 18:26:11 UTC

Package ejabberd-2.1.11-3.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing ejabberd-2.1.11-3.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6401/ejabberd-2.1.11-3.el6
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2012-07-23 20:23:47 UTC

ejabberd-2.1.11-3.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2012-07-23 20:25:29 UTC

ejabberd-2.1.11-3.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2012-07-31 16:57:59 UTC

ejabberd-2.1.11-3.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2012-07-31 17:00:45 UTC

ejabberd-2.1.11-3.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.