From: "Alex Bennée" <alex.bennee@linaro.org>
To: "immersive.excel@gmail.com" <immersive.excel@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] chroot jailing...
Date: Mon, 13 Jan 2014 14:38:25 +0000 [thread overview]
Message-ID: <87wqi4ymji.fsf@linaro.org> (raw)
In-Reply-To: <52D36A12.7090004@gmail.com>
immersive.excel@gmail.com writes:
> Thanks!
>
> So it sounds like you're saying selinux is the only meaningful thing to try?
> Or do people ever bother to place qemu in chroot jails??
>
> I seem to have gotten the impression that people use qemu-static to do this,
> but it appears to be more for offering secured access of a guest folder
> to the host OS;
The qemu-static + chroot approach is mainly to avoid doing complex path
manipulation between host/guest file-systems AFAICT.
> not so much for security...
>
<snip>
--
Alex Bennée
next prev parent reply other threads:[~2014-01-13 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 19:17 [Qemu-devel] chroot jailing immersive.excel
2014-01-13 4:11 ` Stefan Hajnoczi
2014-01-13 4:22 ` immersive.excel
2014-01-13 10:28 ` Markus Armbruster
2014-01-13 14:38 ` Alex Bennée [this message]
2014-01-13 17:07 ` immersive.excel
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=87wqi4ymji.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=immersive.excel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.
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).