This is the mail archive of the
mailing list for the Cygwin project.
Re: Shares with strange ACL settings
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Wed, 12 Aug 2015 20:09:00 +0200
- Subject: Re: Shares with strange ACL settings
- Authentication-results: sourceware.org; auth=none
- References: <loom dot 20150811T101658-176 at post dot gmane dot org> <20150812152601 dot GL13029 at calimero dot vinschen dot de> <loom dot 20150812T172703-7 at post dot gmane dot org> <20150812155817 dot GN13029 at calimero dot vinschen dot de>
Corinna Vinschen writes:
> Cygwin is aware of them and access(2) explicitely checks for them. That
> obviously doesn't help for applications like perl, who "know better"
> than the underlying OS how to evaluate perms.
Perl is making use of an explicit guarantee in POSIX' ACL specification,
placed there in order to be backwards compatible to a system without
ACL. Whether it is a good idea to do this is debatable of course and I
might hunt that code path down in Perl and squash it in some future
release. It nevertheless is chink in Cygwin's shiny armor of "hey,
we're POSIX of the Linux flavor".
FWIW, Git seems to have an explicit check for POSIXPERMS in order to
sort out systems that don't conform exactly to that expectation.
> It does. Another, *very* simple idea is this: Spill the group and
> other perms into the user bits only if the owner of the file is the
> current user. Would that help?
I think so, but there are likely some corner cases. But I think that
had been proposed and shot down already, so I was trying to come up with
something less intrusive.
> But there's no additional checking necessary because the perms are
> guarded by the OS anyway. The applications just don't know them exactly.
I have several scripts where tests for a readable file had to be
replaced with a test for non-zero-size file or just existing file.
Also, with the noacl option you'll always get a positive on most tests
and if the code is unprepared to handle the inevitable failure on the
actual access, then bad things can happen. Not every piece of code has
already converted to the "let's try it and bail out when we get told to
get off" style of file access.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple