Bug 142623

Summary: pam_ccreds.so ends up in /lib/security, not /lib64/security
Product: [Fedora] Fedora Reporter: Rudi Chiarito <nutello>
Component: pam_ccredsAssignee: John Dennis <jdennis>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 1-4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-15 15:41:45 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:
Attachments:
Description Flags
New spec file fixing problems none

Description Rudi Chiarito 2004-12-10 23:26:58 UTC 
Subject really says it all. The module just won't work/load, unless you
move/copy it manually under /lib64/security.

Also, it would probably be a good idea to add pam.conf from the
tarball as a doc file. There's no other documentation anywhere else
in the world (or, at least, the world according to Google) that
explains how to set the module up. And this is a module that is not
easy to set up, even for people that are kinda familiar with pam
configuration files. Unless they're PAM experts, I doubt average
users know about control parameters in square brackets.

There should be support in authconfig, but that's the subject of
another report.
Comment 1 Rudi Chiarito 2005-02-04 21:41:47 UTC 
Created attachment 110678 [details]
New spec file fixing problems

This new spec file fixes the installation path for 64-bit systems and packages
pam.conf in the doc directory. It also fixes bug #134674.