pam config: not yet including common-session modules
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sudo (Debian) |
Fix Released
|
Unknown
|
|||
sudo (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
A simple package configuration issue.
PAM modules like pam_umask, limits and pam_env don't work with sudo because no common-session modules are included in sudo's pam config file.
/etc/pam.d/sudo should be shipped containing
@include common-
If "sudo -i" would really need it, sudo may use and ship two separate configs /etc/pam/
Sudo seems to support pam sessions modules since version 1.7
http://
but they don't get loaded yet.
description: | updated |
summary: |
- common-session pam configuration not included + pam config: not yet including common-session modules |
description: | updated |
Changed in sudo (Ubuntu): | |
status: | New → Confirmed |
description: | updated |
Changed in sudo (Debian): | |
status: | Unknown → New |
Changed in sudo (Debian): | |
status: | New → Fix Committed |
Changed in sudo (Debian): | |
status: | Fix Committed → Fix Released |
Changed in sudo (Ubuntu): | |
status: | Confirmed → Fix Committed |
Sudo seems to be patched to parse /etc/environment itself. With sudo correctly iplementing pam sessions that hack can be reverted. www.sudo. ws/bugs/ show_bug. cgi?id= 83
http://