This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Group Permissions on root folders problem (Windows 10 TP build 10061)
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin at cygwin dot com
- Date: Thu, 10 Sep 2015 12:07:57 -0400
- Subject: Re: Group Permissions on root folders problem (Windows 10 TP build 10061)
- Authentication-results: sourceware.org; auth=none
- References: <CAMH9mcFEL3mao+m-DEYM84kC1HOPeSBpZXD+mDf0USobF9oY7g at mail dot gmail dot com> <CAMH9mcFOKjvjiFvvk1ju0ZxBDK28MaktdnYwj5_CjvbgnpVO4A at mail dot gmail dot com> <20150616155843 dot GE31537 at calimero dot vinschen dot de> <DJzl1r0012qVqVd01Jzm3c> <55F1A69D dot 9050201 at cox dot net>
On 9/10/2015 11:49 AM, David A Cobb wrote:
On a Windows-10 host: when I use Cygwin *chown***or *chmod *to make
permission changes, the next time I access the folder-tree from Windows
Explorer Security tab, it complains that the Access Control List is
incorrectly ordered and that will cause undesirable results; happy to
say, it gives me the chance to re-order the ACL. The usual undesirable
result is that an app can create a folder /New/ within /T/ but cannot
create anything within /T/////New/.
Hypothesis: we are indirectly(?) modifying the ACL but are not observing
whatever Windows expects for ordering. I know that Windows enforces
"*deny*" rules before any "*allow*" rules; I do not know what other
ordering it observes. I do know that Windows doesn't really consider
the "group" property the same way POSIX does, FWIW.
This is explained in the Cygwin User's Guide:
https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-files
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple