If proftpd is emerged with -pam in USE but pam is installed, then proftpd links against pam, and needs to be rebuilt if pam is then unmerged. [ebuild R ] net-ftp/proftpd-1.2.10-r7 -authfile +hardened -ipv6 -ldap -mysql +ncurses -noauthunix -pam -postgres (-selinux) -sendfile -shaper -softquota +ssl +tcpd -xinetd 0 kB * Starting proftpd ... /usr/sbin/proftpd: error while loading shared libraries: libpam.so.0: cannot open shared object file: No such file or directory
Try this patch
Created attachment 65343 [details, diff] Patch to prevent PAM from being enabled despite USE="-pam" Patch to prevent PAM from being enabled despite -pam
The same thing happens (though --disable-pam is being passed to configure) This is from configure btw: checking security/pam_appl.h usability... yes checking security/pam_appl.h presence... yes checking for security/pam_appl.h... yes checking pam/pam_appl.h usability... no checking pam/pam_appl.h presence... no checking for pam/pam_appl.h... no checking for pam_start in -lpam... yes
Try this one:
Created attachment 65347 [details, diff] Pam patch -- part two!
Same thing happens (though --without-pam gets used)
(In reply to comment #6) > Same thing happens (though --without-pam gets used) This sounds like proftpd just not playing by the rules. According to their README.modules, mod_pam is included no matter what if it is found. However, after playing around, I've found a method to stop configure from including it. See attachment.
Created attachment 65351 [details, diff] Last try!
I've tried every combination of those patches I could and at some point it fails due to not finding pam.
Looks like it needs --enable-auth-pam=no passed to configure. There's a hopefully fixed ebuild in Bug 111668, give it a try. # ./configure &> config.log; grep pam config.log checking security/pam_appl.h usability... yes checking security/pam_appl.h presence... yes checking for security/pam_appl.h... yes checking pam/pam_appl.h usability... no checking pam/pam_appl.h presence... no checking for pam/pam_appl.h... no checking for pam_start in -lpam... yes # ./configure --enable-auth-pam=no #
OK, this works for me (didn't get into 1.3.0-r1 unfortunately) <snip> use pam && modules="${modules}:mod_auth_pam" # pam needs to be explicitely disabled - see README.PAM use pam || myconf="${myconf} --enable-auth-pam=no" </snip>
Fixed in net-ftp/proftpd-1.3.0-r2. Thanks for the fix! Best regards, CHTEKK.