Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 12 Feb 2020 08:13:12 -0600
From: "A. Wilcox" <>
Subject: Re: execvp() behaviour with unrecognized file header

On 12/02/2020 07:54, Alexander Scherbatiy wrote:
> Hello,
> execvp() works differently on Linux Alpine and Ubuntu if it is called
> with a file which does not contain a proper shebang line. The file is
> executed on Ubuntu. It results to  ENOEXEC error on Linux Alpine.
> man execvp on Ubuntu has description: "If the header of a file isn't
> recognized (the attempted execve(2) failed with the error ENOEXEC),
> these functions will execute the shell (/bin/sh) with the path of the
> file as its first argument."
> Does execvp() from musl behaves differently by purpose in this case?

This has been discussed before on this list:

Since this is non-conformant to POSIX, Adélie integrated quinq's patch:


A. Wilcox (awilfox)
Project Lead, Adélie Linux

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.