From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: PATCH: safe numeric import
Date: Mon, 29 Sep 2014 08:24:08 -0700 [thread overview]
Message-ID: <140929082408.ZM6204@torch.brasslantern.com> (raw)
In-Reply-To: <20140929110420.52cc66f8@pwslap01u.europe.root.pri>
On Sep 29, 11:04am, Peter Stephenson wrote:
}
} OK, how about this? When we're doing the import, all numbers, integer
} or floating point, are imported straight, without an evaluation.
This looks fine to me. (I'm surprised that there never seems to have
been an IPDEF6 before.)
} Currently we suppress all errors from parameters at this stage, though
} we could make a special case and output errors when we truncate a
} numeric import because we ignored anything after an initial constant.
I could go either way on this one. On the one hand it'd potentially
be nice to get a warning if someone is shoving a strange value through
SHLVL or something. OTOH there's no reason to expect it to work so in
a non-malicious circumstance it shouldn't be necessary.
next prev parent reply other threads:[~2014-09-29 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 14:45 zsh seems to be vulnerable to CVE-2014-6271: remote code execution through bash İsmail Dönmez
2014-09-24 14:54 ` Frank Terbeck
2014-09-24 14:55 ` İsmail Dönmez
2014-09-24 15:01 ` Peter Stephenson
2014-09-24 15:08 ` Frank Terbeck
2014-09-24 15:13 ` Jérémie Roquet
2014-09-24 14:55 ` Jérémie Roquet
2014-09-24 14:59 ` Chet Ramey
2014-09-25 13:11 ` Peter Stephenson
2014-09-26 14:03 ` Oliver Kiddle
2014-09-26 20:08 ` Peter Stephenson
2014-09-29 10:04 ` PATCH: safe numeric import Peter Stephenson
2014-09-29 15:24 ` Bart Schaefer [this message]
2014-10-01 14:57 ` [Bulk] " Oliver Kiddle
2014-10-02 16:06 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=140929082408.ZM6204@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).