Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15454 > unrolled thread
| Started by | L A Walsh <bash@tlinx.org> |
|---|---|
| First post | 2019-10-02 06:26 -0700 |
| Last post | 2019-10-02 06:26 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: shebang-less script execution not resetting some options L A Walsh <bash@tlinx.org> - 2019-10-02 06:26 -0700
| From | L A Walsh <bash@tlinx.org> |
|---|---|
| Date | 2019-10-02 06:26 -0700 |
| Subject | Re: shebang-less script execution not resetting some options |
| Message-ID | <mailman.758.1570022772.2651.bug-bash@gnu.org> |
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 top | Article view | gnu.bash.bug
csiph-web