Our proftpd ebuild includes an ftp file for pam.d which assumes that pam_pwdb.so is available - however this is not built by default for the pam ebuild. We need to supply a default pam.d/ftp file that works with the default pam USE flags. Instead of switching over to pam_unix.so, a better solution would be to go via pam_stack.so with system-auth so that ftp can automagically use ldap or krb5 as well as the ftpusers list.
Created attachment 52127 [details] proposed ftp file for pam.d
Thanks roy, fixed in -r3
-r4 causes this again :(
Yes it does, because it was the way to go to have it working in linux and gentoo. Probably the best way is to go with the extra package to handle the pam stuff UberLord - btw, I'm going to add a net-ftp/pam-base for the ftp pam files like mailbase does Will you handle the inicial and then i'll add the chech for bsd and put the version that uses system-auth
net-ftp/ftpbase is now in portage and supplies a fully working pam.d/ftp file for all pam versions we have - including bsd support. It also adds ftp:ftp user+group if they don't exist, creates their home directory (failing gracefully when /home is ro mounted) and adds the /etc/ftpusers file. vsftpd-2.0.3-r1 depends on this - proftpd and pure-ftpd should do as well - and stop doing things ftpbase now does. AFAIK the other ftp daemons we have in portage don't need this
Fixed in proftpd-1.2.10-r6 pure-ftpd may need this as well at some point - but it would have to be patched to read the /etc/pam.d/ftp file instead of /etc/pam.d/pure-ftp or create a symlink
