| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0004-SHELL-Disable-sh-c-command-sh-c-exec-command-optimiza.diff | shell: Disable sh -c "command" -> sh -c "exec command" optimization Bugs #642706 (bin-prot FTBFS) and #642835 (sexplib310 FTBFS) can be fixed by reverting the patch submitted at [1]. I don't understand why. [1] http://thread.gmane.org/gmane.comp.shells.dash/556 While investigating #642706, in the failing case, I observed that a cpp process called with "sh -c" gets SIGPIPE while writing to stderr. In the succeeding case, the write is successful, and is read by the ocamlbuild process that started "sh -c cpp ...". |
Stéphane Glondu <glondu@debian.org> | no | 2011-09-25 | ||
| 0007-Don-t-execute-binary-files-if-execve-returned-ENOEXE.diff | Don't execute binary files if execve() returned ENOEXEC Both "dash -c foo" and "./foo" are supposed to be able to run hashbang-less scripts, but attempts to execute common binary files tend to be nasty: especially both ELF and PE tend to make dash create a bunch of files with unprintable names, that in turn confuse some tools up to causing data loss. Thus, let's read the first line and see if it looks like text. This is a variant of the approach used by bash and zsh; mksh instead checks for signatures of a bunch of common file types. POSIX says: "If the executable file is not a text file, the shell may bypass this command execution.". |
Adam Borowski <kilobyte@angband.pl> | no | 2017-01-24 | ||
| 0008-Support-e-in-echo-and-printf-builtins.diff | Support \e in "echo" and "printf" builtins | Adam Borowski <kilobyte@angband.pl> | no | 2014-06-28 | ||
| 0009-dash-Fix-stack-overflow-from-infinite-recursion-in-s.patch | dash: Fix stack overflow from infinite recursion in script | Chris Lamb <lamby@debian.org> | no | debian | 2018-02-15 | |
| 0012-enable-large-file-support-when-available.patch | enable large file support when available | You-Sheng Yang <vicamo@gmail.com> | no | 2018-12-12 | ||
| 0013-enable-hardening-for-helpers.patch | Add $(CPPFLAGS), $(CFLAGS) and $(LDFLAGS) to $(COMPILE_FOR_BUILD) so that helpers are built with hardening | Andrej Shadura <andrewsh@debian.org> | no | 2019-07-18 | ||
| 0017-histedit-Fix-infinite-loop-when-using-fc--s.patch | histedit: Fix infinite loop when using 'fc -s' When compiling with libedit, he.num may somehow overrun last, causing an infinite loop when using fc -s. This mild change to the check plugs it. |
宇砂ワシ <usawashi16@yahoo.co.jp> | no | debian | 2019-04-27 | |
| 9001-Add-privmode-Part-1.diff | Implement privmode, part 1 | Tavis Ormandy <taviso@google.com> | no | http://article.gmane.org/gmane.comp.security.oss.general/10969 | 2013-08-22 | |
| 9002-Add-privmode-Part-2.diff | Implement privmode, part 2 | Harald van Dijk <harald@gigawatt.nl> | no | http://article.gmane.org/gmane.comp.security.oss.general/10972 | 2013-08-22 | |
| jobs-Only-block-in-waitcmd-on-first-run.patch | [PATCH] jobs: Only block in waitcmd on first run This patch ensures that waitcmd never blocks unless there are outstanding jobs. This could otherwise trigger a hang if children were created prior to the shell coming into existence, or if there are backgrounded children of other kinds (e.g., a here- document). diff --git a/src/jobs.c b/src/jobs.c index 3417633..516786f 100644 |
Herbert Xu <herbert@gondor.apana.org.au> | no | 2020-12-02 |