vsftpd will not authenticate because pam_ecryptfs.so uses bad paths

[Elyse Grasso]

attemptingMar 9 17:27:50 pavo vsftpd: PAM unable to dlopen(pam_ecryptfs.so): libkeyutils.so.1: failed to map segment from shared object: Cannot allocate memory
Mar 9 17:27:50 pavo vsftpd: PAM adding faulty module: pam_ecryptfs.so
Mar 9 17:27:50 pavo vsftpd: PAM unable to dlopen(pam_pwquality.so): /lib/security/pam_pwquality.so: cannot open shared object file: No such file or directory
Mar 9 17:27:50 pavo vsftpd: PAM adding faulty module: pam_pwquality.so
Mar 9 17:27:50 pavo vsftpd: PAM unable to dlopen(pam_systemd.so): /lib/security/pam_systemd.so: cannot open shared object file: No such file or directory
Mar 9 17:27:50 pavo vsftpd: PAM adding faulty module: pam_systemd.so
Mar 9 17:27:50 pavo vsftpd: PAM unable to dlopen(pam_ck_connector.so): /lib/security/pam_ck_connector.so: cannot open shared object file: No such file or directory
Mar 9 17:27:50 pavo vsftpd: PAM adding faulty module: pam_ck_connector.so
Mar 9 17:27:50 pavo vsftpd: PAM unable to dlopen(pam_mkhomedir.so): /lib/security/pam_mkhomedir.so: cannot open shared object file: No such file or directory
Mar 9 17:27:50 pavo vsftpd: PAM adding faulty module: pam_mkhomedir.so
 to log in to vsftpd fails with a 530 and puts the following into the auth.log:

The only file in /lib/security is pam_ecryptfs.so itself -- everything else is in architecture specific locations. It seems to have been created with obsolete paths. Are there symbolic links missing from /lib/security that would compensate for this? (I tried loading the i386 pam libs in case that was what it was looking for, but that did not help.)

Are there configuration changes I can make that will let vsftpd work AND still let me log into my encrypted home directory? I'm nervous about breaking something and locking myself out if I experiment too much.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: vsftpd 3.0.2-1ubuntu2.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
Date: Mon Mar 9 18:16:00 2015
ExecutablePath: /usr/sbin/vsftpd
InstallationDate: Installed on 2012-04-26 (1047 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SourcePackage: vsftpd
UpgradeStatus: Upgraded to trusty on 2014-09-02 (188 days ago)
modified.conffile..etc.pam.d.vsftpd: [deleted]
modified.conffile..etc.vsftpd.conf: [modified]
mtime.conffile..etc.vsftpd.conf: 2015-03-09T15:58:30.619148

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robie Basak (racb)]

The first error was "Cannot allocate memory". So could this be another instance of bug 1348972?

[Robie Basak (racb)]

I'm passing by looking at old bugs. I didn't set Importance last time I was here. I'm setting Importance to Low now, because use of pam_ecryptfs with vsftpd appears to be an uncommon use case.