This problem affects us, and is quite severe: Kerberized NFS cannot work
reliably and securely with lxdm unless it is fixed. Because the
Kerberos cache is discarded, users cannot reliably get access to
Kerberos-protected home directories. The retain_after_close workaround
almost entirely
Using retain_after_close may work as a temporary work around, but it
does not fix the bug.
The fact that using retain_after_close will prevent the clearing of the
credentials cache on login is a strong hint that to what the bug is. It
now seems very likely that 'lxdm' is closing the just created
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxdm (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937602
Title:
lxdm
Use
authoptionalpam_krb5.so minimum_uid=1000 try_first_pass
retain_after_close
session optionalpam_krb5.so minimum_uid=1000
retain_after_close
retain_after_close will tell to PAM to no to clear the ticket after it
completes. So it will stay.
--
You
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/937602
Title:
lxdm clears kerberos ticket cache on login
To manage notifications about this bug go to:
