[Bug 253096] Re: pam_umask.so not called in /etc/pam.d/common-session{, -noninteractive}
Steve Langasek
steve.langasek at canonical.com
Mon Jun 6 09:42:33 UTC 2011
** Changed in: pam (Ubuntu)
Status: New => Triaged
** Changed in: pam (Ubuntu)
Importance: Undecided => Medium
** Changed in: pam (Ubuntu)
Assignee: Steve Langasek (vorlon) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/253096
Title:
pam_umask.so not called in /etc/pam.d/common-session{,-noninteractive}
Status in “pam” package in Ubuntu:
Triaged
Bug description:
The pam_umask.so module determines the umask (from system and user
config files) and sets it for users accordingly.
from /etc/login.defs:
# the use of pam_umask is recommended as the solution which
# catches all these cases on PAM-enabled systems.
The umask itself should not be set in /etc/pam.d/common-account, but
pam_umask needs to be called from there.
The system's default UMASK remains in /etc/login.defs, setting it in
common-account would override login.defs *and* any user specific
configs in gecos fields, see man pam_umask.
The option "usergroups" is neccessary to have pam_umask check if the
user has a private user group and re-enables appropriate group
permission setting for save and easy user collaboration (Info in Bug
#252351).
The line needed to call pam_umask in /etc/pam.d/common-account is:
session optional pam_umask.so usergroups
(This reflects the settings that are in /etc/login.defs, but have not
been working since pam broke it.)
More information about the foundations-bugs
mailing list