From: Vince Rice <vrice@solidrocksystems.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Empty file without "x" permission is successfully executable on Cygwin
Date: Tue, 06 Aug 2019 21:06:00 -0000 [thread overview]
Message-ID: <CD9BE2EF-CC1B-4BC1-B0FB-036D98D33E81@solidrocksystems.com> (raw)
In-Reply-To: <BL0PR0901MB4308F5C32DC6C1B5C22F373BA5D50@BL0PR0901MB4308.namprd09.prod.outlook.com>
> On Aug 6, 2019, at 3:39 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via wrote:
>
>> But what's your basis for saying that an empty script shouldn't be executable?
>
> I meant it only in the context of the script file lacking the proper "x" permission.
> Of course an empty script _with_ such permissions allowed must be executable, and it will always complete with exit code 0.
Which is why, as Ken said, the size is irrelevant. What's relevant is that it shouldn't be executing
anything that doesn't have the executable bit set. Which is what Corinna fixed.
--
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
next prev parent reply other threads:[~2019-08-06 21:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 20:39 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-06 21:06 ` Vince Rice [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-06 22:28 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-06 21:17 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-06 21:43 ` Vince Rice
2019-08-06 19:09 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-06 19:35 ` Ken Brown
2019-08-07 6:12 ` Houder
2019-08-24 10:13 ` Houder
2019-08-05 18:18 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-05 20:01 ` Ken Brown
2019-08-05 20:19 ` Thomas Wolff
2019-08-05 20:39 ` Ken Brown
2019-08-06 3:19 ` Ken Brown
2019-08-06 8:33 ` Corinna Vinschen
2019-08-06 9:01 ` Corinna Vinschen
2019-08-06 6:22 ` Houder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CD9BE2EF-CC1B-4BC1-B0FB-036D98D33E81@solidrocksystems.com \
--to=vrice@solidrocksystems.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).