Bug 191149 - configure pam for netgroups
Summary: configure pam for netgroups
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pam
Version: 5
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-09 08:57 UTC by M.T
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-05-09 11:14:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description M.T 2006-05-09 08:57:40 UTC
Description of problem:
WE have set-up a linux server with FC5, (64bit), here in our department. We run
also nis, and we need to set-up the linux server, so as only certain nis
netgroups, have access on it.
I have configure the /etc/pam.d/sshd with 
account    required     /lib/security/pam_access.so
and also I add the following to /etc/security/access.conf
 -:ALL EXCEPT @RESEARCH:ALL , since I need to give access through ssh, only to
netgroup RESEARCH. 

When I try to login with an account that belongs to group RESEARCH, i got the
following:
May  9 10:05:26 thales sshd[9425]: PAM unable to dlopen(/lib/security/pam_access.so)
May  9 10:05:26 thales sshd[9425]: PAM [error: /lib/security/pam_access.so:
wrong ELF class: ELFCLASS32]
May  9 10:05:26 thales sshd[9425]: PAM adding faulty module:
/lib/security/pam_access.so
May  9 10:05:28 thales sshd[9425]: Failed password for userxx from xxx.xx.xx.xxx
port 40612 ssh2
M

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tomas Mraz 2006-05-09 11:14:41 UTC
This is a misconfiguration or broken installation.

First you shouldn't use absolute paths to modules (simple pam_access.so should
be enough) as that will make problems on multilib systems such as ia64 or x86_64.

Also what prints rpm -V pam?



Note You need to log in before you can comment on or make changes to this bug.