I think there's two bugs here:
1. If you autologin and PAM_USER is changed in a PAM module LightDM must abide
by that.
2. There's no method to do an autologin without explicitly specifying a PAM
user.
** Changed in: lightdm
Status: New => Triaged
** Changed in: lightdm
Importance: Undecided => Medium
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: lightdm/1.10
Importance: Undecided
Status: New
** Changed in: lightdm/1.10
Importance: Undecided => Medium
** Changed in: lightdm/1.10
Status: New => In Progress
** Changed in: lightdm (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: lightdm (Ubuntu Trusty)
Status: New => Triaged
** Changed in: lightdm (Ubuntu Utopic)
Status: New => Triaged
** Changed in: lightdm (Ubuntu Utopic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371710
Title:
autologin should support PAM_USER
Status in Light Display Manager:
Triaged
Status in Light Display Manager 1.10 series:
Triaged
Status in “lightdm” package in Ubuntu:
Triaged
Status in “lightdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Utopic:
Triaged
Bug description:
There should be a way to specify the autologin-user via PAM_USER.
Currently, to enable autologin you specify autologin-user in the
lightdm.conf file, and any value of PAM_USER returned after
pam_authenticate() is ignored.
This means if you want to affect autologin so that different users are
logged in at different times, based on some external criteria, you
must rewrite the lightdm configuration and restart the service each
time.
One approach would be to add a new key e.g. "autologin-user-pam=true"
which would enable autologin and use the PAM_USER returned by
pam_authenticate() as the user to log in. It might make sense that if
PAM_USER is *not* set by the call to pam_authenticate to fall back to
the autologin-user value, or else to disable autologin entirely.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1371710/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
