This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Problem with "None" Group on Non-Domain Members
- From: "Chris J. Breisch" <chris dot ml at breisch dot org>
- To: cygwin at cygwin dot com
- Date: Mon, 05 May 2014 10:17:00 -0400
- Subject: Re: Problem with "None" Group on Non-Domain Members
- Authentication-results: sourceware.org; auth=none
- References: <536796E4 dot 2090009 at breisch dot org> <20140505135928 dot GK30918 at calimero dot vinschen dot de>
Corinna Vinschen wrote:
On May 5 09:49, Chris J. Breisch wrote:
As far as Cygwin tools are concerned, the None group is just a normal
group like any other group. The behaviour you're observing looks a bit
like either your group file is not ok, or you're testing this with the
noacl mount option. Or, probably more likely, you're suffereing from
the default ACL settings propagated from the parent directory.
When Cygwin sets the POSIX permissions, it does exactly the same thing
for the primary group in your token, whether it's None or any other
group.
I understand what you're saying, but I don't think the behavior agrees
with your statements. I've tried this on a couple different machines,
and the behavior is identical. No matter what I do, if a file is created
with the "None" group, the group file permissions are always identical
to the owner file permissions. I've tried playing with my umask and with
directory sticky bits. It doesn't matter. In the example above, my
parent directory is rather oddly, Chris.Users 000. The current directory
is Chris.None 775.
$ ls -ld . ..
drwxrwxr-x+ 1 Chris None 0 May 5 10:05 ./
d---------+ 1 Chris Users 0 May 5 09:35 ../
And again, changing the permissions of the directory doesn't accomplish
anything:
$ chmod 755 .
$ ls -ld . ..
drwxrwxr-x+ 1 Chris None 0 May 5 10:08 ./
d---------+ 1 Chris Users 0 May 5 10:08 ../
Changing the group for the directory doesn't help either:
$ chgrp Users .
$ touch bar
$ ls -l bar
-rw-rw-r-- 1 Chris None 0 May 5 10:10 bar
$ chmod 600 bar
$ ls -l bar
-rw-rw---- 1 Chris None 0 May 5 10:10 bar
$ ls -ld . ..
drwxrwxr-x+ 1 Chris Users 0 May 5 10:10 ./
d---------+ 1 Chris Users 0 May 5 10:08 ../
Taking the example one step farther:
$ chmod 600 bar
$ ls -l bar
-rw-rw---- 1 Chris None 0 May 5 10:10 bar
$ chmod 400 bar
$ ls -l bar
-r--r----- 1 Chris None 0 May 5 10:10 bar
And changing the group from "None" to anything else always fixes the
permission issues. chmod and umask suddenly start working as expected.
--
Chris J. Breisch
--
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