I don't see anything here that's a bug in the pam package.
> when I am working with the Freetz build-system I have this
> umask/shell problem described in [1].
It is a bug for any build system to make assumptions about the umask.
If particular permissions are required, it should set them explicitly -
or set its own umask as part of the build system.
> The umask is "002" when xterm is started.
That is the current default, yes.
> $ man pam_umask
> ...recommends:
> EXAMPLES
> Add the following line to /etc/pam.d/login to set the user
> specific umask at login:
This is an example, not a recommendation. Modifying the
/etc/pam.d/login file only affects the login service. As you are not
using a console login, this does not apply.
> NOTE-1: common-session is a INCLUDED file, but a
> dpkg -S /path/to/common-session does NOT refer to any Ubuntu package.
This is normal for config files modified by the system at runtime, and
is not a bug in pam. It is arguably a bug in dpkg, but not one that
will be fixed any time in the near future.
> NOTE-2: session items in common-session file are malformed (tabs)!
There's nothing malformed about using tabs here.
> I am not sure where exactly to change the umask for shell logins
> GLOBALLY and/or USER-DEFINED.
In the /etc/pam.d/common-session* include files, where the existing
references to pam_umask are found.
** Changed in: pam (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097262
Title:
[pam][pam_umask]: Explicitly set the user specific umask at (shell)
login to "0022" value
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1097262/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
