From: jazz AT softway DOT com (Jason Zions)
Subject: Re: cygwin32 NT4.0 NTFS - problem?
1 Dec 1997 22:33:50 -0800
Message-ID: <3483157E.17B64A67.cygnus.gnu-win32@opennt.com>
References: <34827681 AT Oslo4GW DOT Norway DOT NCR DOT COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Patrik Wennberg - NCR <PATRIK AT Oslo4GW DOT Norway DOT NCR DOT COM>
Cc: "'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>

The NTFS security model doesn't distinguish between users and groups;
each ACE in an ACL identifies a security principal (either user or
group) and lists the principal's access rights. A file has an owner,
which is any security principal (again, can be a group). A file also has
a primary group, but I think NTFS enforces this to actually be a group
and not a user.

By default, Win32 frequently makes the Administrators *group* the owner
of any file created by any member of the Administrators group. Typical
ACLs would have two entries: an ACE for the Administrators group and an
ACE for Everyone. Cygwin has to somehow map those two ACEs into the
classical Unix mode bits; something someplace is *always* going to
appear odd when an ACL doesn't have exactly an ACE for the owner, an ACE
for a group, and an ACE for everyone/authenticated users/whatever cygwin
thinks "Unix Other" maps to.

Jason
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".