X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5D3313857703 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1681892432; bh=3vo0EzpEjlfER7UkFCiOLJ8Ru2Mk+fz4xaHdvU+ZvU0=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=kTLPdp73LjnGtIiUtUGhJuB5yHZt/fcAhbeWRrJLRWjfQqk3gTYvPVPHch8Ez92AM xyKNo8IC7gUAlCFqi1L/OqsptCfi6hRWVCjSkJJnCHJ6bcPD+EzX9IqdD7CXWYfHlA nNnpVbMNWg+qwDjuWqHt5wKkNHoAzp5EmbkzRM+g= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F18A53858D1E Date: Wed, 19 Apr 2023 10:19:55 +0200 To: Eric Blake Subject: Re: posix_spawn facility Message-ID: Mail-Followup-To: Eric Blake , Bruno Haible , cygwin AT cygwin DOT com References: <1752276 DOT 7aRn1RRit1 AT nimes> <1741636 DOT G7SD5HZVK5 AT nimes> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen , Bruno Haible , cygwin AT cygwin DOT com Content-Type: text/plain; charset="utf-8" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 33J8KvZ3021783 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 -- 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