** Description changed: 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 is - set in /etc/login.defs, and setting it here would override it and all - user specific configs (see man pam_umask). + 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.)
-- pam_umask.so missing in common-account https://bugs.launchpad.net/bugs/253096 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
