Thank you for taking the time to report this bug and help to improve
Ubuntu.
There is nothing dynamic about what umask value that should be used for
a given user, and there are already well-established means of setting
the umask for a session (which will only be further confused if we add
another method on top of that), so this is not a change that Ubuntu
should adopt. It's possible that there are places where a wrong umask
is being set by default; those would be bugs, and should be fixed, but
they are not bugs in pam, and should not be worked around by adding
complexity to the default pam config.
Also, I cannot corroborate your statement that setting umasks by the
usual method doesn't work for login sessions. It certainly does for me.
You may want to provide more detail about your use case.
The example syntax you gave is also invalid. The pam_umask module in
intrepid does not recognize a 'usergroups' option.
** Changed in: pam (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
Status: New => Won't Fix
--
pam_umask.so missing in common-session
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
