Re: shebang-less script execution not resetting some options

From	L A Walsh <bash@tlinx.org>
Newsgroups	gnu.bash.bug
Subject	Re: shebang-less script execution not resetting some options
Date	2019-10-02 06:26 -0700
Message-ID	<mailman.758.1570022772.2651.bug-bash@gnu.org> (permalink)
References	(1 earlier) <5D9334F8.3090503@tlinx.org> <20191001124135.GJ28751@eeg.ccf.org> <5D9477C6.2000002@tlinx.org> <895e1eb5-d3be-c6fe-8e12-b98765a2b167@iki.fi> <5D94A56B.2000003@tlinx.org>

Show all headers | View raw


On 2019/10/02 03:49, Ilkka Virta wrote:
>
>          If the execl() function fails due to an error equivalent to the
>          [ENOEXEC] [...] the shell shall execute a command equivalent to
>          having a shell invoked with the pathname resulting from the
>          search as its first operand, [...]
>
> [ 
> https://pubs.opengroup.org/onlinepubs/9699919799.2018edition/utilities/V3_chap02.html#tag_18_09_01_01 
> ]
>
> -----
>
> I think that last sentence above is the relevant part. The standard only 
> says to "invoke a shell". It doesn't say which shell, probably because 
> it only specifies one.
>   
POSIX probably doesn't mandate secure passwords, firewalls, malware
detection,
etc.  Just because posix doesn't require it, doesn't mean it is a good idea
to ignore it.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: shebang-less script execution not resetting some options L A Walsh <bash@tlinx.org> - 2019-10-02 06:26 -0700

csiph-web