From: Harald van Dijk <harald@gigawatt.nl>
To: dash <dash@vger.kernel.org>
Subject: Re: How to pass parameters containig options from variables
Date: Tue, 25 Sep 2012 20:55:32 +0200 [thread overview]
Message-ID: <5061FE24.3000300@gigawatt.nl> (raw)
In-Reply-To: <1C74D9CF-5354-4197-BBF1-F7E9FC1AE681@aim.com>
On 25-9-2012 18:48, Paul Gilmartin wrote:
> On Sep 25, 2012, at 10:28, bd@bc-bd.org wrote:
>>> eval $DAEMON $ARGS should work.
>> That did it, thank you.
> ... but always beware of "eval" if you don't absolutely
> control the argument string. A single semicolon and
> someone owns your process.
For a configuration file that gets sourced, the person creating the
configuration file already owns the process, so there is no added
security by avoiding eval here.
prev parent reply other threads:[~2012-09-25 19:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 8:47 How to pass parameters containig options from variables bd
2012-09-25 13:21 ` Olof Johansson
2012-09-25 16:28 ` bd
2012-09-25 16:48 ` Paul Gilmartin
2012-09-25 18:55 ` Harald van Dijk [this message]
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=5061FE24.3000300@gigawatt.nl \
--to=harald@gigawatt.nl \
--cc=dash@vger.kernel.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.
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).