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:reply-to:to:subject:date:message-id
	:content-type:content-transfer-encoding:mime-version; q=dns; s=
	default; b=kl10vRTibtQ71wQfGG5pkgwCFkrxx4cUw6oScHvjw9SK7zHO7MMbm
	8HRG//VbLypBuJGuk3kKStM92O0o92G773ny9NWdbmyebzNuWxWbnNoq9JDX+9PV
	fijMkXKMX6DPQY0SHrcrOrxDhLJZdEf7ksaxY1DldP090295+jZ2sw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
IronPort-SDR: 1k0I12IEKSceUOZ2jRH0JvUoAMM61zZmFO65NO0+G50tefIqji3l47DCImuMA6g4NFvktgMkn/ 8FSSTqQQ7x+FcI9DCxjlQ6Bx9IUmUCUcDVGoolA/l/jaJMQS6UGbSKk9kbtOOlTmvI9J1Hhsqf zD1MMgNJUFwT1x57e8kVdXRBgsPEazS6ajMB9+Aciq1oCuJXRd2hATvyVCAQLe+imiQ0aJOE25 Kvhr/55DYuXHZrnJIpPCru04kP42o1GmJuV7B7b3kxld4DSxWL5Lgx2f82EhaIpZMW7XSx7VNy +RI=
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin" <cygwin@cygwin.com>
Reply-To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Re: SMBFS mount's file cannot be made executable
Date: Wed, 14 Aug 2019 00:53:32 +0000
Message-ID: <BN6PR09MB14096842C04FD9783DC9C260A5AD0@BN6PR09MB1409.namprd09.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-userprincipalname: eKr/cks9wwSe3hf3oS0WzOUf2Ai+0pVgyLiyhZdzIFbnefDX4cG5IInuTN7kFIdT
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x7E0sTuO007118

> If it's related to the ACL handling then it should start working when
> you remove the ACL on the file with 'setfacl -kb ...'

There are no special ACLs set on the file (that was just produced by GCC from the source code, see my first email).

But I am now convinced that the problem is _entirely_ in Cygwin's corner:

When I open that file's the "Properties->Security" Windows tab, I can see that my permissions are "Read" and "Write", yet
"Read & Execute" is NOT checked.  When I check it, I see that the file becomes executable (the "x" bit) from both
Cygwin shell and on the Linux side, too.  And after that, I can execute the file from the Cygwin shell.

So what happens is that when "chmod" (or "creat" with a permission mask) is called, Cygwin does not honor the "x" bit(s) and does not convert it to
a corresponding proper ACL for the Windows mounted filesystem (and that ACL, in turn, would have been then sent to SMBD to get converted there back
to the "x" bit in the Unix world).  Once the "x" is there, Windows(via SMBD) obviously allows execution of the image.  Here's a related "bug":

https://forge.univention.org/bugzilla/show_bug.cgi?id=33785

I did not investigate in details how Cygwin handles the execute permission, but obviously there's something off.


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