Does not set PAM_XDISPLAY and or XDISPLAY, XAUTHORITY variables
Bug #862559 reported by
Wolfgang Ullrich
This bug affects 38 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Light Display Manager |
Fix Released
|
Medium
|
Unassigned | ||
lightdm (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
If a PAM module with GUI interface for alternative authentication methods (like fingerprint authentication) is used, this module needs information about the xdisplay to connect to for showing up it's widget. Therefore PAM has two enviroment variables to be setup by the application before calling the "pam_authenticate" function. These variables are PAM_XDISPLAY and PAM_TTY, both to be set to the current display number (e.g. ":0"). Alternatively the environment variables XDISPLAY and XAUTHORITY can be set, so the PAM module can get the information by calling "getenv()".
Changed in lightdm (Ubuntu): | |
importance: | Medium → Low |
Changed in lightdm: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
PAM_TTY has been set since 0.9.7. PAM_XDISPLAY is not currently set. XAUTHORITY is set later in the process, as it requires the home directory to be mounted. We could set it to a system XAUTHORITY earlier then replace it with the user XAUTHORITY.