> Errexit (a.k.a. set -e) is horrible,
> and you should not be using it in any new shell scripts you write.
> It exists solely for support of legacy scripts.
Wow. For those of us who don't know this, what should we be using instead? Is
using a trap on ERR any better? Is your suggestion that ||
[I am terribly sorry that my In-Reply-To is wrong :/]
- Eric Blake ebl...@redhat.com wrote:
... Remember, the security hole of
Shell Shock is NOT what the function is named, but the fact that
arbitrary variable contents were being parsed. ...
Not quite: the point of exploit can be in the
- Ángel González an...@16bits.net wrote:
The patch seems straightforward:
diff --git a/variables.c b/variables.c
index 92a5a10..6552e69 100644
--- a/variables.c
+++ b/variables.c
@@ -361,7 +361,7 @@ initialize_shell_variables (env, privmode)
...
- if (legal_identifier (name))
CFLAGS='-O2 -m32 -g') and mkbuiltins.o was compiled without -m32 (as it uses
CCFLAGS_FOR_BUILD, which bypasses CFLAGS to use BASE_CCFLAGS) but was being
linked with -m32. I do not yet have a correct fix for this unrelated issue.
Sincerely,
Jay Freeman (saurik)
sau...@saurik.com
http://www.saurik.com
On Mar 18, 6:55 pm, m...@ice.filescope.com, zy...@ice.filescope.com
wrote:
...
When I type a long string of text and start pressing ctrl-W to
backwards-kill words, bash deletes the words but doesn't visually refresh
(the words still appear on the command line). This was not occurring
/trunk/data/readline/cflags.diff
Sincerely,
Jay Freeman (saurik)
sau...@saurik.com
http://www.saurik.com/
