After studying the code and exploring a bit with gdb and a test PAM module I wrote that simply sets pam_user, I've determined that in fact lightDM *already* works just fine with a PAM module on the auth stack of the lightdm-autologin PAM service which sets PAM_USER. I simply hadn't realized that autologin used its own PAM service.
The name specified for PAM_USER will override the autologin-user value in lightdm.conf. In my opinion, this behavior is ideal. If we actually tried to change the code to allow turning autologin on without specifying an autologin user, and no PAM_USER was set by any PAM module, we'd have a strange error case to deal with. So, to turn autologin on, you must specify a default/fallback user for autologin-user. If a PAM module in the lightdm-autologin PAM stack sets PAM_USER in pam_sm_authenticate(), that will override the user specified in lightdm.conf. No change required. If there are no other suggestions/objections, I will close out this bug. Too bad, I was looking forward to contributing :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371710 Title: autologin should support PAM_USER To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1371710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
