All of lore.kernel.org
 help / color / mirror / Atom feed
From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] qemu context
Date: Tue, 27 Jul 2010 09:10:08 -0700	[thread overview]
Message-ID: <4C4F04E0.2000500@gmail.com> (raw)
In-Reply-To: <20100727155149.GA10237@localhost.localdomain>

On 07/27/2010 08:51 AM, Dominick Grift wrote:
> On Tue, Jul 27, 2010 at 06:29:55AM -0700, Justin P. Mattock wrote:
>> hello,
>>
>> probably can just post on iirc for a faster response..but decided
>> to e-mail instead.. Anyways I've qemu finally running
>> after some time of not using it and wanted to know what/where
>> might I look too get info on the file labels for this.
>>
>> right now i've an .img in my home directory(not in var/lib/*)
>> the context is
>> ls -lZ name:name name:object_r:virt_image_t:s0 *.img
>>
>> is this seem correct?
>
> In fedora there is a qemu_image_t type for qemu images.
>

cool thanks for the response..
was looking at some wikis and stuff I'll have todo some more reading on 
this.

from what I see so far libvirt plays an important role(I think) but 
still need to look into it.

So far my setup, is a simple build of qemu-kvm, added the udev rule so I 
dont run as root,and my *.img is in the home directory(still debating if 
I need libvirt).

main concern is making the virtual os confined so if it gets 
exploited(sorry winxp) my main system is not touched or exploited(if it 
ever gets to that point)

Justin P. Mattock

  reply	other threads:[~2010-07-27 16:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 13:29 [refpolicy] qemu context Justin P. Mattock
2010-07-27 15:51 ` Dominick Grift
2010-07-27 16:10   ` Justin P. Mattock [this message]
2010-07-27 16:27     ` Dominick Grift
2010-07-27 16:46       ` Justin P. Mattock

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=4C4F04E0.2000500@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=refpolicy@oss.tresys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.