X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=cy76mRyr1PzC7zb9
	MBRWFebKr/CH79maX+5jMDFF/411PQRL8gcW8/nV1TqnR+5PuLBPLq+19M7n/pKn
	Oc10RK6y/H6mRYwOUT9UeHB1yYtIR5TDlzIWfLOX2P77N32uDwyhoHCg7Sckr3/t
	4vQ8DgO7AfW/Mni9B7VP/Y0B4Wg=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=xaZaDxWd95Q+Hnl5NvhjKD
	yqAG4=; b=WsDg4OaJLxZx73SMhyxeC4AVOqWVf8euQ+R1Qn0Jp3AsLipJ0nANTk
	izRLXndY4egxDnVa18WE7hA2P/vd5eyTZXq4a/g09Bdo1umzK2K8v26dwCWUrHPB
	ztDKsi8Dr99uQfEwUHzVrXcIWX2yi5Ufn7qxBGZc1tpIJAuaVS/pc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtpback.ht-systems.ru
Date: Tue, 11 Mar 2014 16:30:47 +0400
From: Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To: cygwin AT cygwin DOT com
Message-ID: <542902046.20140311163047@yandex.ru>
To: Charles Plager <cplager AT gmail DOT com>, cygwin AT cygwin DOT com
Subject: Re: File permissions when using ACLs
In-Reply-To: <CAKfFMLQe3L3q_qJ-=07KiCQwraqQYP3jbB-8fohZaH9-7PWnSg@mail.gmail.com>
References: <CAKfFMLQe3L3q_qJ-=07KiCQwraqQYP3jbB-8fohZaH9-7PWnSg AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Charles Plager!

> Short version: When writing to network drives (and probably local
> ones) as Cygwin is setup by default, we see the permissions being set
> using the ACLs where "creator owner"  is given "full control" and
> "creator" group are given "read/execute", but by setting "special
> permissions" instead of just having "full control" or "read/execute"
> set.

> Why does it not just set "full control" or "read/execute"?

Cygwin by default mimicking POSIX permission set.
If this behavior is undesirable, You can work around it by letting operating
system control the ACL.
Modify cygdrive entry in /etc/fstab to include noacl option.
Then any files accessed outside direct/implied mounts will have permissions
controlled by OS.

> Long, slightly different version: When the above permissions get set,
> we sometimes see (sometimes = 1 file in a million or less) a file that
> ends up with no permissions.  Owner loses permissions, admin loses
> permissions and so far, IT has only been able to make the file go away
> by reformatting the drive.

> When we tell Cygwin not to use ACLs (adding the following in
> /etc/fstab), this does not seem to happen (in 100 million or so files
> created).

> none /cygdrive/ cygdrive binary,posix=0,user,noacl 0 0


> This only seems to happen for files created by Cygwin with the ACL
> permissions (although, to be fair, without Cygwin, I don't know that
> anybody is generating as many files).  I'm assuming it isn't Cygwin,
> per say, but rather something that interacts with how Cygwin setup the
> permissions (and given the rarity of the problem it is difficult to
> diagnose more thoroughly.

> So, to sum up:

> * Why use special permissions and not default settings when using ACLs?

> * Anybody else experience  files that lose all permissions?  Any
> suggestions on resetting the file (short of reformatting the drive)?

> * Any other hints/insights that might be useful here?

> Thanks,
>   Charles

> p.s.  We see this behavior for Cygwin 1.7.9 and beyond.  In 1.7.5, it
> doesn't appear as if the ACLs are used and it acts as if "noacl" is
> set.


--
WBR,
Andrey Repin (anrdaemon AT yandex DOT ru) 11.03.2014, <16:08>

Sorry for my terrible english...


--
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