DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 6B37D3858D1E
To: cygwin@cygwin.com, Eric Blake <eblake@redhat.com>
Subject: Re: posix_spawn facility
Date: Wed, 19 Apr 2023 00:10:34 +0200
Message-ID: <1741636.G7SD5HZVK5@nimes>
In-Reply-To: <xsn3qmrcprucviwtwoehm5hfgna5nogttqgud3ut6t2craprjp@6u5dgtopjfig>
References: <1752276.7aRn1RRit1@nimes> <ZD5h973pS0tVenD0@calimero.vinschen.de>
 <xsn3qmrcprucviwtwoehm5hfgna5nogttqgud3ut6t2craprjp@6u5dgtopjfig>
MIME-Version: 1.0
Precedence: list
From: Bruno Haible via Cygwin <cygwin@cygwin.com>
Reply-To: Bruno Haible <bruno@clisp.org>
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

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

Bruno


-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple