From: Anthony Liguori <anthony@codemonkey.ws>
To: Vincent Hanquez <tab@snarc.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Paul Brook <paul@codesourcery.com>,
Alexandre Bique <bique.alexandre@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] ATAPI pass through v2
Date: Wed, 08 Jul 2009 13:06:09 -0500 [thread overview]
Message-ID: <4A54E011.6090204@codemonkey.ws> (raw)
In-Reply-To: <20090708174829.GA7078@snarc.org>
Vincent Hanquez wrote:
> On Wed, Jul 08, 2009 at 12:20:59PM -0500, Anthony Liguori wrote:
>
>>>> I'm sure something like SELinux can be used to prevent a root QEMU
>>>> process from doing a firmware upgrade.
>>>>
>>>>
>>> *boggle* You're not serious, are you ?
>>>
>>>
>> Yes, I'm actually a fan of SELinux in the context of a dedicated
>> virtualization system.
>>
>
> do you really expect to put a SCSI packet inspector (to detect firmware update
> for example) in a SELinux layer ?
>
SELinux uses LSM to provide security hooks for enforcement so if there
isn't already, one would add an LSM hook in the Linux ATAPI driver for
firmware updates.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-07-08 18:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 18:31 [Qemu-devel] [PATCH 0/5] ATAPI pass through v2 Bique Alexandre
2009-07-07 20:03 ` Stuart Brady
2009-07-07 21:21 ` Alexandre Bique
2009-07-07 22:44 ` Paul Brook
2009-07-07 22:50 ` Alexandre Bique
2009-07-07 23:01 ` Anthony Liguori
2009-07-07 23:15 ` Stuart Brady
2009-07-08 16:09 ` Ian Jackson
2009-07-08 16:38 ` Avi Kivity
2009-07-08 17:28 ` Carl-Daniel Hailfinger
2009-07-08 18:03 ` Anthony Liguori
2009-07-08 18:09 ` Avi Kivity
2009-07-08 17:20 ` Anthony Liguori
2009-07-08 17:48 ` Vincent Hanquez
2009-07-08 18:06 ` Anthony Liguori [this message]
2009-07-07 22:58 ` Anthony Liguori
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=4A54E011.6090204@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Ian.Jackson@eu.citrix.com \
--cc=bique.alexandre@gmail.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=tab@snarc.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).