SCIENTIFIC-LINUX-USERS Archives

November 2005

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"John A. Goebel" <[log in to unmask]>
Reply To:
John A. Goebel
Date:
Thu, 10 Nov 2005 09:06:42 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (92 lines)
++ 10/11/05 14:31 +0100 - <Stefan Sabolowitsch>:

Hey,

> Hi List,
> 
> OS = SL Linux 4.1 x86_64 (with latest updates)
> 
> If I want to connect with the ftp (proftpd) server, I get the following
> error message.
> 
> Nov 10 14:09:49 linuxsrv3 proftpd[3785]: linuxsrv3.feltengmbh.de
> (192.168.1.68[192.168.1.68]) - FTP session opened. 
> Nov 10 14:09:49 linuxsrv3 proftpd: PAM unable to
> dlopen(/lib/security/pam_listfile.so)
> Nov 10 14:09:49 linuxsrv3 proftpd: PAM [dlerror:
> /lib/security/pam_listfile.so: cannot open shared object file: No such file
> or directory]
> Nov 10 14:09:49 linuxsrv3 proftpd: PAM adding faulty module:
> /lib/security/pam_listfile.so
> Nov 10 14:09:49 linuxsrv3 proftpd: PAM unable to
> dlopen(/lib/security/pam_pwdb.so)
> Nov 10 14:09:49 linuxsrv3 proftpd: PAM [dlerror: /lib/security/pam_pwdb.so:
> cannot open shared object file: No such file or directory]
> Nov 10 14:09:49 linuxsrv3 proftpd: PAM adding faulty module:
> /lib/security/pam_pwdb.so
> Nov 10 14:09:49 linuxsrv3 proftpd[3785]: linuxsrv3.feltengmbh.de
> (192.168.1.68[192.168.1.68]) - PAM(stefan): Module is unknown.
> 
> The solution is here.
> 
> I checked the /lib/security/ folder, and those files do exist, and they have
> all of the right ownership and permissions.
> One of the other things I mentioned was that I was using SL Linux x86_64.
> My install has two lib folders. /lib/ and /lib64/ and they each contain a
> security folder with all of the PAM modules.
> I changed my /etc/pam.d/ftp file to point into the /lib64/security/ folder
> and IT WORKED.
> I could log in.
 
Another fix is to you the $ISA variable. It's supported in Pam for SL4.

The syntax is:

/lib/security/$ISA/pam_pwdb.so

$ISA determines architecture and modifies the path to the correct value. This
is a help especially if you use cfengine or something homebrewed to modify
files. Both 32- and 64-bit pam.d files will be the same.

John
 
> I just looked at a bunch of the other pam.d files, and I noticed that many
> of them were pathless in their definition of specific PAM modules.
> I tried this in the pan.d/ftp file, and it still worked.
> There must be some configuration in pam that allows it to find the correct
> module.
> 
> I suggest that in future releases that the ftp file should not list explicit
> paths.
> 
> I hope this helps someone else.
> 
> Stefan Sabolowitsch
> 
> 
> Administrator IT
> 
> 
> FELTEN GmbH
> In den Dörrwiesen 31
> D-54455 Serrig
> Tel: +49 (65 81) 91 69 - 25
> Fax: +49 (65 81) 91 69 - 33
> E-Mail: [log in to unmask]
> www.feltengmbh.de
> www.pm-scada.de
> _____________________ Confidentiality ______________________
> This electronic transmission is strictly confidential and intended 
> solely for the addressee. It may contain information which is covered 
> by legal, professional or other privilege. If you are not the intended 
> addressee, you must not disclose, copy or take any action in reliance 
> of this transmission. If you have received this transmission in error, 
> please notify us and delete the received data as soon as possible.
> 

##############################################
# John Goebel <jgoebel(at)slac.stanford.edu> #
# Stanford Linear Accelerator Center         #
# 2575 Sand Hill Road, Menlo Park, CA 94025  #
############################################ #

ATOM RSS1 RSS2