From: Rob Landley <rob@landley.net>
To: "Edgar E. Iglesias" <edgar.iglesias@axis.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] -chroot and -su options.
Date: Wed, 5 Mar 2008 00:51:36 -0600 [thread overview]
Message-ID: <200803050051.36813.rob@landley.net> (raw)
In-Reply-To: <20080304112212.GA9347@edgar.se.axis.com>
On Tuesday 04 March 2008 05:22:12 you wrote:
> On Mon, Mar 03, 2008 at 06:28:22PM -0600, Rob Landley wrote:
> > Quick and dirty patch to teach qemu application emulation how to chroot
> > (and drop privs), so you don't have to pollute a target filesystem with
> > host code, and/or figure out how to build qemu static in order to run a
> > dynamic binary.
>
> Hi Rob,
>
> Right, doing the chroot from within qemu avoids the issue with polluting
> the target/. Thanks for the example.
>
> The chroot approach still suffers from the need of initially having higher
> privileges. Personally, I still prefer the sysroot option and avoid that
> need but either way helps me.
>
> Best regards
Which sysroot option? (I may have missed a patch, I'm a month behind on the
list. This is just something I've meant to submit for... about a year, I
think.)
You can also teach a bunch of different qemu syscalls (open, unlink, mmap,
exec, fcntl, and 3 dozen others...) to append a prefix to its path, and
perhaps try to prevent them from playing games with symlinks or ".." to break
out of that subdir. But that's a much, much, much more extensive/intrusive
patch.
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2008-03-05 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 0:28 [Qemu-devel] [PATCH] -chroot and -su options Rob Landley
2008-03-04 11:22 ` Edgar E. Iglesias
2008-03-05 6:51 ` Rob Landley [this message]
2008-03-05 7:54 ` Edgar E. Iglesias
2008-03-06 6:47 ` Rob Landley
2008-03-14 14:08 ` Edgar E. Iglesias
2008-03-14 15:26 ` Rob Landley
2008-03-14 16:06 ` Anderson Lizardo
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=200803050051.36813.rob@landley.net \
--to=rob@landley.net \
--cc=edgar.iglesias@axis.com \
--cc=qemu-devel@nongnu.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).