ecryptfs-setup-private breaks with ldap user accounts
Bug #317307 reported by
Tessa
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Fix Released
|
Wishlist
|
Dustin Kirkland | ||
ecryptfs-utils (Ubuntu) |
Fix Released
|
Medium
|
Dustin Kirkland |
Bug Description
Binary package hint: ecryptfs-utils
On my intrepid amd64 system (ecryptfs-
$ ecryptfs-
ERROR: User [ldapusername] does not exist
$ ecryptfs-
ERROR: User [ldapusername] does not exist
All other programs see the user account fine, including "getent passwd".
Related branches
Changed in ecryptfs-utils (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in ecryptfs: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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