GNU Core Utilities - Bugs: bug #28891, Fix all code that sets the umask...
You are not allowed to post comments on this tracker with your current authentication level.
bug #28891: Fix all code that sets the umask to zero
Submitter: | Matt McCutchen <hashproduct> | ||
Submitted: | Sat 13 Feb 2010 09:51:29 PM UTC | ||
Votes: | 20 | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 20 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2014-09-09 | chewi | Carbon-Copy | - | ![]() |
Added chewi |
2012-08-08 | mjo | Carbon-Copy | - | ![]() |
Added mjo |
2010-02-13 | hashproduct | Carbon-Copy | - | ![]() |
Added hashproduct |
Several pieces of code in coreutils set the umask to zero in order to create files with specific permissions:
Code that takes this approach generally doesn't handle default ACLs properly. Here's an example with mkdir(1):
The code should be fixed to call chmod(2) on the created files, and then the umask is no longer relevant.