This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: ACL behavior in Cygwin // Re: (call-process ...) hangs in emacs
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Thu, 28 Aug 2014 20:29:14 +0200
- Subject: Re: ACL behavior in Cygwin // Re: (call-process ...) hangs in emacs
- Authentication-results: sourceware.org; auth=none
- 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>
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