From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Eric Blake <eblake@redhat.com>
Cc: Bruno Haible <bruno@clisp.org>, cygwin@cygwin.com
Subject: Re: posix_spawn facility
Date: Wed, 19 Apr 2023 10:19:55 +0200 [thread overview]
Message-ID: <ZD+kK0mMzqCS6Vj0@calimero.vinschen.de> (raw)
In-Reply-To: <wqmniudnbjv4rdm4wa5a4lxbfoipvmdmsvi646ndaksfgne4s3@4xfdvvdd4g62>
On Apr 18 21:39, Eric Blake via Cygwin wrote:
> On Wed, Apr 19, 2023 at 12:10:34AM +0200, Bruno Haible wrote:
> > Eric Blake wrote:
> > > we now have implementations in the wild that differ in behavior, and
> > > use security as a reason for the divergence, it is worth getting that
> > > clarified in POSIX. I'll file a bug against POSIX shortly
> >
> > For the reference, the systems that return ENOEXEC for posix_spawnp
> > attempting to execute a script without #! marker are:
> > - glibc/Linux ≥ 2.15
> > - glibc/Hurd ≥ 2.33 (commit 13adfa34aff03fd9f1c1612b537a0d736ddb6c2b)
> > - musl libc
>
> POSIX issue now filed as
> https://www.austingroupbugs.net/view.php?id=1674; although we'll have
> to see if my wording is acceptable or if it settles on something a bit
> looser (such as implementation-defined as to whether an sh fallback is
> attempted, rather than outright forbidden).
Thank you!
Corinna
next prev parent reply other threads:[~2023-04-19 8:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 11:46 Bruno Haible
2023-04-17 9:18 ` Corinna Vinschen
2023-04-17 18:44 ` Bruno Haible
2023-04-18 9:25 ` Corinna Vinschen
2023-04-18 20:49 ` Eric Blake
2023-04-18 21:00 ` Corinna Vinschen
2023-04-18 22:10 ` Bruno Haible
2023-04-19 2:39 ` Eric Blake
2023-04-19 8:19 ` Corinna Vinschen [this message]
2023-04-19 11:56 ` Bruno Haible
2023-04-20 6:52 ` Csaba Raduly
2023-07-31 18:58 ` Eric Blake
2023-07-31 19:12 ` Corinna Vinschen
2023-04-19 8:24 ` Corinna Vinschen
2023-04-19 11:24 ` posix_spawn_file_actions_add[f]chdir_np Bruno Haible
2023-04-19 15:05 ` posix_spawn_file_actions_add[f]chdir_np Corinna Vinschen
2023-04-19 19:13 ` posix_spawn_file_actions_add[f]chdir_np Corinna Vinschen
2023-04-19 21:33 ` posix_spawn_file_actions_add[f]chdir_np Eliot Moss
2023-04-20 10:27 ` posix_spawn_file_actions_add[f]chdir_np Bruno Haible
2023-04-19 10:48 ` posix_spawn facility Bruno Haible
2023-04-20 7:14 ` gs-cygwin.com
2023-04-20 8:35 ` Corinna Vinschen
2023-04-20 10:18 ` Bruno Haible
2023-04-20 14:21 ` Corinna Vinschen
2023-04-20 14:40 ` Corinna Vinschen
2023-04-20 14:58 ` Bruno Haible
2023-04-20 15:40 ` Corinna Vinschen
2023-04-20 18:46 ` gs-cygwin.com
2023-04-20 18:40 ` gs-cygwin.com
2023-04-20 19:31 ` Bruno Haible
2023-04-20 20:00 ` gs-cygwin.com
2023-05-10 9:15 ` gs-cygwin.com
2023-04-20 18:04 ` gs-cygwin.com
2023-05-10 8:59 ` gs-cygwin.com
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=ZD+kK0mMzqCS6Vj0@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=bruno@clisp.org \
--cc=cygwin@cygwin.com \
--cc=eblake@redhat.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).