From: "David Windsor" <dwindsor@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: David Windsor <dwindsor@tresys.com>,
kvm-devel <kvm-devel@lists.sourceforge.net>,
James Morris <jmorris@namei.org>,
qemu-devel <qemu-devel@nongnu.org>,
selinux <selinux@tycho.nsa.gov>,
Joshua Brindle <jbrindle@tresys.com>
Subject: [Qemu-devel] Re: [kvm-devel] [RFC][PATCH 00/01]qemu VM entrypoints
Date: Fri, 20 Jul 2007 17:57:29 -0400 [thread overview]
Message-ID: <25a1d91b0707201457m6865a505maf93d22c5c28f0cc@mail.gmail.com> (raw)
In-Reply-To: <Line.LNX.4.64.0707201628150.9702@d.namei>
On 7/20/07, James Morris <jmorris@namei.org> wrote:
> On Fri, 20 Jul 2007, Daniel P. Berrange wrote:
>
> > It could be - if your put the policy at the control API layer instead of
> > in QEMU itself.
>
I think that libvirt may be a bit too high in the virtualization stack
for this control.
What benefits are there for placing such a hook in libvirt vs qemu?
libvirt could still use the vm:entrypoint permission for other types
of VMs it manages.
> Then you can bypass MAC security by invoking qemu directly.
>
>
> - James
> --
> James Morris
> <jmorris@namei.org>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
next prev parent reply other threads:[~2007-07-20 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C2C68600.366D%dwindsor@tresys.com>
2007-07-20 21:50 ` [Qemu-devel] [RFC][PATCH 00/01]qemu VM entrypoints David Windsor
[not found] ` <46A1151F.7020502@codemonkey.ws>
2007-07-20 21:55 ` [Qemu-devel] Re: [kvm-devel] " David Windsor
2007-07-20 22:19 ` Anthony Liguori
[not found] ` <20070720201101.GC12218@redhat.com>
[not found] ` <Line.LNX.4.64.0707201628150.9702@d.namei>
2007-07-20 21:57 ` David Windsor [this message]
2007-07-20 23:50 ` Daniel P. Berrange
2007-07-21 1:41 ` James Morris
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=25a1d91b0707201457m6865a505maf93d22c5c28f0cc@mail.gmail.com \
--to=dwindsor@gmail.com \
--cc=berrange@redhat.com \
--cc=dwindsor@tresys.com \
--cc=jbrindle@tresys.com \
--cc=jmorris@namei.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=selinux@tycho.nsa.gov \
/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).