From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Cc: 415996@bugs.debian.org
Subject: Re: [Qemu-devel] [PATCH] Re: option to have qemu chroot() into the target filesystem
Date: Sat, 25 Oct 2008 11:09:58 +0300 [thread overview]
Message-ID: <f43fc5580810250109j3e42376er40f6a5e9973d56fa@mail.gmail.com> (raw)
In-Reply-To: <200810241806.10698.rob@landley.net>
On 10/25/08, Rob Landley <rob@landley.net> wrote:
> On Friday 24 October 2008 04:21:29 Bernhard Reutner-Fischer wrote:
> > A patch was in this thread:
> > http://www.mail-archive.com/qemu-devel@nongnu.org/msg16297.html
> >
> > Rob promised to respin it tomorrow and resend it in to the list.
> > thanks
>
> The debian bug report in question is:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=415996
>
> I checked and the old patch still applies cleanly (well, with an offset, but
> no fuzz). I applied it and then did an svn diff, the result of which is
> attached. (As with all svn diffs, it applies with "patch -p0 -i blah.patch")
>
> It's actually a very simple patch, which does this:
>
> A) Teach qemu-$TARGET to do a chdir() plus chroot() in response to a -chroot
> command line option.
>
> B) Because A) requires root access, teach qemu-$TARGET to change uid and gid
> via a -su option (and set both the real and effective user IDs so it's
> actually dropping priviledges).
Because the UID change happens at argument parse stage, doesn't the
chrooting fail if the -su option is specified in the command line
before -chroot?
prev parent reply other threads:[~2008-10-25 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081024092129.GA5952@mx.loc>
2008-10-24 23:06 ` [Qemu-devel] [PATCH] Re: option to have qemu chroot() into the target filesystem Rob Landley
2008-10-25 8:09 ` Blue Swirl [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=f43fc5580810250109j3e42376er40f6a5e9973d56fa@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=415996@bugs.debian.org \
--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).