From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Empty file without "x" permission is successfully executable on Cygwin
Date: Sat, 24 Aug 2019 10:13:00 -0000 [thread overview]
Message-ID: <9b61d432ff036788aec774109d57dc3d@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <f7311e1f60cba7ebae136109f077d2d4@smtp-cloud9.xs4all.net>
On Wed, 07 Aug 2019 08:12:28, Houder wrote:
> On Tue, 6 Aug 2019 19:09:04, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin" wrote:
> > > zero-sized? Irrelevant.
> >
> > It is actually very relevant. Because executing an empty script results in=
> > "success" (exit code 0) -- that creates a false-positive.
[snip]
> What I meant, was: a regular file (empty or not), but w/o shebang and w/o the
> execute bit, will be executed by Cygwin, contrary to what happens on Unix.
>
> This behaviour (again: different from Unix) has existed for at least a decade.
>
> That is why I wrote: Cygwin != Linux.
>
> When I found out, years and years ago, I assumed that the deviation was due
> to FAT filesystems (not being able to represent the x-bit).
>
> Perhaps I was wrong. Perhaps the Cygwin maintainers merely goofed up long ago.
And again I was wrong ...
- https://cygwin.com/ml/cygwin/2009-06/msg00721.html
( Re: Cygwin 1.7: Possible file permission errors in 'base-files' )
"I've put that on my TODO list."
- https://cygwin.com/ml/cygwin/2009-06/msg00727.html
( HEADSUP maintainers: Packages install scripts without execute permissions )
"I have the patch for this ready ..."
Now that the problem has been fixed by Corinna, she can remove it from her TODO
list :-P
Henri
--
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-24 5:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [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 20:39 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-06 21:06 ` Vince Rice
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=9b61d432ff036788aec774109d57dc3d@smtp-cloud8.xs4all.net \
--to=houder@xs4all.nl \
--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).