DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=g+K
	XPHHCkZLkDpXqymXv02HwtLBlTuazaMJs3yZAGx/Dg/7m0u+OfbpUPW9TuWAziSO
	2gMGMoa2bookPy7Cq1RomEuVp44rCq3h7mF/LYEGsD8xvC+lcHYsBuzwMcJ6I5CP
	+1YMmv1HEBUm5yLFTZ5bFI3p6ngLmqTPYGkgmD1Q=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Achim Gratz <Stromeko AT NexGo DOT DE>
Subject: Shares with strange ACL settings
Date: Tue, 11 Aug 2015 08:42:10 +0000 (UTC)
Lines: 53
Message-ID: <loom.20150811T101658-176@post.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
User-Agent: Loom/3.14 (http://gmane.org/)

I've thought some more about those strange shares I need to use that have
inherited ACL that don't let me change the ACL at all and hence prevent
Cygwin from fixing up the POSIX permissions.  That generally ends up with
permissions like these:

% ll test
total 10
d---rwx---+ 1 gratz          Domain Users    0 Aug 10 11:51 ./
d---rwx---+ 1 Administrators Administrators  0 Aug 10 11:50 ../
----rwx---+ 1 gratz          Domain Users   18 Aug 10 11:51 blafasel*
----rwx---+ 1 gratz          Domain Users   18 Aug 10 11:51 blumblum*

Some applications that know how POSIX ACL are supposed to work conclude that
such directories or files are not readable:

% cd test
% perl -E 'say -r "." ? "readable" : "not readable";'
not readable
% perl -E 'say -r "blafasel" ? "readable" : "not readable";'
not readable

Other applications not using this shortcut and going all the way to
faccessat correctly determine readability:

% [ -r . ] && echo readable || echo not readable
readable
(1056)/mnt/upload/test > [ -r blafasel ] && echo readable || echo not readable
readable

If I access the files from another account (that has the same group
memberships that give read/write access to the share) or change the owner,
then the shortcut is never invoked:

$ perl -E 'say -r "." ? "readable" : "not readable";'
readable
$ perl -E 'say -r "blafasel" ? "readable" : "not readable";'
readable
$ [ -r . ] && echo readable || echo not readable
readable
$ [ -r blafasel ] && echo readable || echo not readable
readable

So, it would probably help if I had a mount option to force the ownership to
some account that I am never logged in as, either via a mount option or
whenever the POSIX user modes are all cleared.  I don't know if that might
confuse applications when they check ownership on newly created files,
though.  Is that something that is implementable easily so it could be
tested via a snapshot?


Regards,
Achim.


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