Just a stock, default config with those modules installed.
common-auth:
# here are the per-package modules (the Primary block)
auth[success=2 default=ignore] pam_unix.so nullok_secure
auth[success=1 default=ignore] pam_lsass.so try_first_pass
# here's the fallback if no module
And now I see the problem, even. It’s in common-session:
session sufficient pam_lsass.so
session optionalpam_ecryptfs.so unwrap
…it never gets to the pam_ecryptfs.so because pam_lsass is sufficient.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This also partly explains why consolekit stuff doesn’t work properly for
these users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920609
Title:
likewise-open users with migrated home directory
ok, looks like a bug in the likewise-open package then. reassigning.
** Package changed: ecryptfs-utils (Ubuntu) = likewise-open (Ubuntu)
** Changed in: likewise-open (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks, all! I'm actually going to re-add the ecryptfs-utils task and
mark it invalid there, as this question has come up more than once.
Hopefully that will make this more discoverable.
** Also affects: ecryptfs-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
This has to do with the pam stack. It could either be an
incompatibility with pam_ecryptfs and whatever pam module likewise-open
uses, or perhaps just a missing bit of pam configuration in the
/etc/pam.d stack.
Subscribing Steve Langasek... Any ideas, Steve?
** Changed in: ecryptfs-utils
I agree it probably has to do with the pam stack. What do /etc/pam.d
/common-auth and /etc/pam.d/common-session look like on the affected
system?
** Changed in: ecryptfs-utils (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of
