Issue #22051 has been updated by Dustin Mitchell.

Status changed from Unreviewed to Duplicate

http://msdn.microsoft.com/en-us/magazine/cc982153.aspx (Understanding Windows 
File And Registry Permissions) says that the primary group is only used for 
POSIX compatibility, which is why it's pretty difficult to see with any normal 
Windows tools.

So Windows gives you enough space to create permissions equivalent to any 
combination of POSIX user/group/mode, but that mapping is not 1:1 nor even 
onto.  Multiple (equivalent) POSIX u/g/m combinations can map to the same 
security descriptor.  And this bug is an example of such.

So, basically, we need #13249.

----------------------------------------
Bug #22051: Windows mode bits are not handled symmetrically
https://projects.puppetlabs.com/issues/22051#change-96264

* Author: Dustin Mitchell
* Status: Duplicate
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* Affected Puppet version: 
* Keywords: 
* Branch: 
----------------------------------------
As far as I can tell, Windows mode bits are read as CCE, where C is the 
creator/owner perms, and E is the everyone perms.  So a file that's rwx for 
creator/owner but with no perms for anyone else would appear to puppet as 770.  
If you have permissions bits with different user and group triplets, Puppet 
resets the permissions on every run.

For example,

    file {
        'c:/foo.txt':
            mode => 0644;
    }

will change the mode from 0664 to 0644 on every run.

It seems like some folding of bits in the provider could work around this 
pretty easily.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to