From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Non-stub gettext API functions committed, ready for testing
Date: Sun, 27 Jul 2014 14:00:41 -0400 [thread overview]
Message-ID: <20140727180041.GA4038@brightrain.aerifal.cx> (raw)
In-Reply-To: <20140727175125.GI10402@port70.net>
On Sun, Jul 27, 2014 at 07:51:26PM +0200, Szabolcs Nagy wrote:
> > >From what I can tell, that's not so bad. Anyone feel like writing an
> > expression evaluator for it? I think recursive descent is fine as long
> > as the length of the string being evaluated is capped at a sane length
> > (or just keep a depth counter and abort the evaluation if it exceeds
> > some reasonable limit).
> >
>
> i can try
OK. Some thoughts on implementation: It should probably accept the
expression as a base+length rather than a C string so it can be used
in-place from within the mo file "header" (this design might help for
recursion anyway I suppose). And it should be safe against malicious
changes to the expression during evaluation (at worst give wrong
results or error out rather than risk of stack overflow, out-of-bounds
reads, etc.) since I'm aiming to make the whole system safe against
malicious translation files (assuming the caller doesn't use the
results in unsafe ways like as a format string).
Rich
next prev parent reply other threads:[~2014-07-27 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 8:46 Rich Felker
2014-07-27 10:06 ` Harald Becker
2014-07-27 14:14 ` Szabolcs Nagy
2014-07-27 16:49 ` Rich Felker
2014-07-27 17:23 ` Szabolcs Nagy
2014-07-27 17:36 ` Rich Felker
2014-07-27 17:51 ` Szabolcs Nagy
2014-07-27 18:00 ` Rich Felker [this message]
2014-07-28 10:18 ` Szabolcs Nagy
2014-07-28 13:00 ` Szabolcs Nagy
2014-07-28 14:01 ` Szabolcs Nagy
2014-07-28 16:27 ` Rich Felker
2014-07-29 13:49 ` Szabolcs Nagy
2014-07-27 10:19 ` Harald Becker
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=20140727180041.GA4038@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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/musl/
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).