http://bugs.winehq.org/show_bug.cgi?id=34406
Erich Hoover erich.e.hoover@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #12 from Erich Hoover erich.e.hoover@gmail.com --- (In reply to comment #10)
(In reply to comment #8)
According to this article : http://technet.microsoft.com/en-us/library/cc783530%28v=ws.10%29.aspx
it appears that write permission on a folder implies read permissions.
I can't find that assumption in that article: ...
In the table it shows that when Write permission is granted (column) then special "Read Permissions" are achieved (row). I'm not sure this is actually the case after doing some testing.
(In reply to comment #11)
... sid: S-1-1-0, mask: 0x120116, flags: 0 sid: S-1-5-18, mask: 0x1f01ff, flags: 13 sid: S-1-5-32-544, mask: 0x1f01ff, flags: 13 sid: S-1-3-0, mask: 0x10000000, flags: 1b sid: S-1-5-32-545, mask: 0x1200a9, flags: 13 sid: S-1-5-32-545, mask: 0x116, flags: 12
Excellent, that confirms my original theory then - it is the inherited permissions that allow this folder to be read. So, that would make this somewhat related to Bug #33576, the fix is the same - but that bug is about specific permissions not being recalled rather than the permissions being inherited from the parent folder. I'm currently maintaining a set of patches for this as part of the Silverlight/PlayReady work I've been doing, so it'd be worth applying those patches and giving that a try: https://github.com/compholio/wine-compholio-daily/tree/master/patches/02-ACL...