Jira (PUP-2293) mode 'ug+w' affects other bits

2 views
Skip to first unread message

Maggie Dreyer (JIRA)

unread,
May 16, 2017, 2:41:04 PM5/16/17
to puppe...@googlegroups.com
Maggie Dreyer updated an issue
 
Puppet / Bug PUP-2293
mode 'ug+w' affects other bits
Change By: Maggie Dreyer
Team: Agent
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Maggie Dreyer (JIRA)

unread,
May 16, 2017, 2:41:04 PM5/16/17
to puppe...@googlegroups.com
Maggie Dreyer updated an issue
Change By: Maggie Dreyer
Labels: triaged

Moses Mendoza (JIRA)

unread,
May 18, 2017, 1:56:48 PM5/18/17
to puppe...@googlegroups.com
Moses Mendoza updated an issue
Change By: Moses Mendoza
Labels: triaged

Josh Cooper (Jira)

unread,
Jan 27, 2021, 1:17:04 AM1/27/21
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-2293
 
Re: mode 'ug+w' affects other bits

Puppet works this way because it applies symbolic modes relative to Puppet::Util::DEFAULT_POSIX_MODE which is defined as. Puppet doesn't apply the symbolic mode relative to the source file's mode. See https://github.com/puppetlabs/puppet/blob/6.20.0/lib/puppet/type/file.rb#L908.

Puppet has always worked this way since symbolic modes were introduced in https://github.com/puppetlabs/puppet/commit/2ac94f94b9af6d8025ee0e771c4c7141ca9705c6#diff-909c0342abb4e713d05ed12ca713a199fd7fb79bc68927cef4e9b2e14726a684R740.

In theory, puppet could be modified to retrieve the source file's mode, and apply the symbolic mode relative to that. However, it's non-trivial due to local vs remote sources, managing file content via the content or source parameter, and source_permissions defaults to ignore. Given that, I'm going to close this issue as won't do.

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages