ecryptfs team mailing list archive

[Lee Maguire <lee-debian@xxxxxxxxxxxx>]

Finding references to /etc/passwd and replacing with genent calls helps (see attached diff).

However the use of  /sbin/unix_chkpwd for password verification will
apparently fail for LDAP due to the ordering in /etc/pam.d/common-
password (pam_unix first, then pam_ldap).  You can use --loginpass to
bypass this issue.

http://osdir.com/ml/linux.pam/2007-04/msg00008.html

** Attachment added: "Replace references to /etc/passwd"
   http://launchpadlibrarian.net/21807950/ecryptfs-setup-private_ldap.diff

-- 
ecryptfs-setup-private breaks with ldap user accounts
https://bugs.launchpad.net/bugs/317307
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” source package in Ubuntu: New

Bug description:
Binary package hint: ecryptfs-utils

On my intrepid amd64 system (ecryptfs-utils-53-1ubuntu12), running ecrypt-setup-private from an LDAP provided user account breaks:

$ ecryptfs-setup-private 
ERROR: User [ldapusername] does not exist
$ ecryptfs-setup-private --username ldapusername
ERROR: User [ldapusername] does not exist

All other programs see the user account fine, including "getent passwd".