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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=ZJucX
	yTwMBikX7i8pmOyVnXztfW6oz6LqEHc20SN7wCDiescHimkI4vA4ly2vmpLIwmV+
	W3L7ArzzH3byNNb/7aXG94guWE2FCFzC8D30iI+UmDxLpg0zI5Wuz5YenD3w6kUx
	iYtEf6BXl2lAQAXTojck2vPMQIzFRvH5JAOC/E=
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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; s=default; bh=xs5HXBm23PS
	b4k2c1wQEeUvKyU0=; b=uXRq31z1M69g+GwRPrCxZQIrbdSXVv7o6jzST56XwSw
	zExW40FWCMy0UGdyKpz8YQDOHh8CBmvKP3JDd3Q5cMngy/dVxNGxuCcspu5fCsNj
	78/VKXwdG769CdWtzvKOVsQNOVU0wGVFCAUW2H1UlndbctW4XhPd+dIkRWmx9//Q
	=
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=-0.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPAM_URI,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-in-09.arcor-online.net
X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-14.arcor-online.net 598AF9BDF4
From: Achim Gratz <Stromeko AT nexgo DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: ACL behavior in Cygwin // Re: (call-process ...) hangs in emacs
References: <53E3F2AE DOT 7030608 AT redhat DOT com> <53E4D01B DOT 9010005 AT cornell DOT edu>	<53F1F154 DOT 1020702 AT cornell DOT edu> <53FB87DC DOT 2050908 AT cornell DOT edu>	<87wq9v9j2y DOT fsf AT Rainer DOT invalid> <53FD0662 DOT 5050208 AT cornell DOT edu>	<20140827084245 DOT GD20700 AT calimero DOT vinschen DOT de>	<17910052714 DOT 20140828010203 AT yandex DOT ru>	<20140828100112 DOT GQ20700 AT calimero DOT vinschen DOT de>	<187704841 DOT 20140828172337 AT yandex DOT ru>	<20140828141036 DOT GW20700 AT calimero DOT vinschen DOT de>	<1833268701 DOT 20140828210041 AT yandex DOT ru>
Date: Thu, 28 Aug 2014 20:29:14 +0200
In-Reply-To: <1833268701.20140828210041@yandex.ru> (Andrey Repin's message of	"Thu, 28 Aug 2014 21:00:41 +0400")
Message-ID: <87fvgglb7p.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.93 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Andrey Repin writes:
>> What Cygwin could do is to perform ACL-based access checks independently of
>> the "acl"/"noacl" mount mode on FSes supporting ACLs.  However, if you want
>> ACLs, why not use the "acl" mount mode in the first place?
>
> ACL inheritance, mostly. POSIX'ized permissions break inheritance on newly
> created files, at times making these files inaccessible to native
> applications, even though inheritance rules would allow it otherwise.

You can prevent this from happening if you forbid users to change the
ACL and enforce inheritance.  That's the reason I can't give those files
sensible POSIX permissions since they'd need to be translated into ACL
which I can't write.  All our filers are set up that way.  No I don't
think this is a good idea, but I guess there'd been one support call too
many with a share that somebody made inaccessible by fiddling with the
ACL.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

DIY Stuff:
http://Synth.Stromeko.net/DIY.html

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