~/.pam_environment not parsed by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Light Display Manager |
Invalid
|
High
|
Robert Ancell | ||
at (Ubuntu) |
Fix Released
|
Undecided
|
Gunnar Hjalmarsson | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
gdm (Ubuntu) |
Fix Released
|
High
|
Gunnar Hjalmarsson | ||
Precise |
Fix Released
|
Medium
|
Gunnar Hjalmarsson | ||
lightdm (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Gunnar Hjalmarsson | ||
openssh (Ubuntu) |
Fix Released
|
Undecided
|
Gunnar Hjalmarsson | ||
Precise |
Fix Released
|
Undecided
|
Colin Watson | ||
pam (Ubuntu) |
Invalid
|
High
|
Gunnar Hjalmarsson | ||
Precise |
Invalid
|
Undecided
|
Unassigned | ||
sudo (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Precise |
Invalid
|
Undecided
|
Unassigned |
Bug Description
lightdm precise and gdm precise SRU proposals
-------
[Impact]
As was originally stated in the bug summary, ~/.pam_environment is not read at login if $HOME is encrypted. The lightdm (Precise) and gdm (Precise) SRUs fix that issue.
[Test Case]
Steps to reproduce:
* As a user with an ecryptfs protected $HOME, use language-selector to make the user language and/or user regional formats differ from the system wide settings (i.e. ~/.pam_environment != /etc/default/
* Log out and log in again. Run the locale command from a terminal window, and with the old version you'll find that the output is a result of /etc/default/
[Regression Potential]
Low.
openssh precise SRU proposal
-------
As lightdm/gdm, but log in via an ssh session instead. (This can just be 'ssh localhost'.)
Previous description
-------
PAM needs to be told explicitly by respective service to parse ~/.pam_environment, since the fix of http://
Otherwise the session environment will contain the system wide locale settings, while the user's locale settings are ignored.
CVE References
Changed in lightdm: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in lightdm: | |
importance: | Medium → High |
Changed in lightdm (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in lightdm (Ubuntu Precise): | |
assignee: | nobody → Robert Ancell (robert-ancell) |
Changed in pam (Ubuntu): | |
importance: | Undecided → High |
Changed in pam (Ubuntu): | |
milestone: | none → ubuntu-13.04-feature-freeze |
Changed in openssh (Ubuntu): | |
status: | New → Triaged |
Changed in openssh (Ubuntu Precise): | |
status: | New → Triaged |
summary: |
- ~/.pam_environment not parsed when HOME is encrypted + ~/.pam_environment not parsed by default |
Changed in lightdm (Ubuntu): | |
assignee: | Robert Ancell (robert-ancell) → Gunnar Hjalmarsson (gunnarhj) |
status: | Triaged → In Progress |
description: | updated |
description: | updated |
Changed in openssh (Ubuntu Precise): | |
assignee: | nobody → Colin Watson (cjwatson) |
status: | Triaged → In Progress |
tags: |
added: verification-done-precise removed: verification-precise-done |
When dealing with this bug, it would be great if bug #957431 could be addressed as well. I suppose that the latter bug requires code changes in about the same spot in the source as this one.