ecryptfs team mailing list archive

[Dustin Kirkland <dustin.kirkland@xxxxxxxxx>]

On Fri, Jan 30, 2009 at 12:49 PM, Lee Maguire <lee-debian@xxxxxxxxxxxx> wrote:
> 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.

Hi Lee-

About "--loginpass" ...  What is this an option to?

It's not valid against unix_chkpwd, or getent.

I'd like to try and solve the password checking portion of this problem.

:-Dustin

-- 
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: Triaged

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".