|
Bugzilla – Full Text Bug Listing |
| Summary: | umask value will not be set for user root | ||
|---|---|---|---|
| Product: | Sudo | Reporter: | Ferenc Ulrich <ulrich.ferenc> |
| Component: | Sudo | Assignee: | Todd C. Miller <Todd.Miller> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | low | ||
| Version: | 1.8.20 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
|
Description
Ferenc Ulrich
2019-10-11 07:24:35 MDT
At one point the PAM session code run after sudo had set the umask, effectively overriding the umask sudo set itself. In the current code, PAM session modules run before sudo sets the umask so the documentation needs to be updated to reflect this. If you want to have the umask set by pam_umask preserved, add the following line to your sudoers: Defaults !umask Sudo 1.8.29 will contain a change that allows PAM to override the default umask set by sudo. However, if the umask is explicitly set in sudoers it will override the value set by PAM. I think this is a reasonable compromise. The commit in question is: https://www.sudo.ws/repos/sudo/rev/7c0a835ac512 Thanks :) Fixed in sudo 1.8.29 |