From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] kernel_corenetwork.te.in.patch
Date: Fri, 04 Jun 2010 16:32:25 -0400 [thread overview]
Message-ID: <4C0962D9.10300@redhat.com> (raw)
In-Reply-To: <1275666210.809.56.camel@gorn.columbia.tresys.com>
On 06/04/2010 11:43 AM, Christopher J. PeBenito wrote:
> On Fri, 2010-06-04 at 10:53 -0400, Daniel J Walsh wrote:
>> On 06/04/2010 09:52 AM, Christopher J. PeBenito wrote:
>>> On Wed, 2010-06-02 at 16:18 -0400, Daniel J Walsh wrote:
>>>> http://people.fedoraproject.org/~dwalsh/SELinux/F14/kernel_corenetwork.te.in.patch
>>>>
>>>> tun_tap_device is an mls trusted object
>>>
>>> Why? This seems wrong to me.
>
>> I think virtual machines at different levels need to talk to this device.
>
> But there are several of these devices. Making it trusted means that
> theres no separation between the networks, which seems contrary to what
> a MLS system would want. More likely, the MLS label needs to be changed
> as needed.
>
I think the kernel will take care of the isolation.
Eric Dan, Is tuntap device per qemu instance?
next prev parent reply other threads:[~2010-06-04 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 20:18 [refpolicy] kernel_corenetwork.te.in.patch Daniel J Walsh
2010-06-04 13:52 ` Christopher J. PeBenito
2010-06-04 14:53 ` Daniel J Walsh
2010-06-04 15:43 ` Christopher J. PeBenito
2010-06-04 20:32 ` Daniel J Walsh [this message]
[not found] ` <20100607093019.GB19864@redhat.com>
2010-06-07 12:45 ` Christopher J. PeBenito
-- strict thread matches above, loose matches on Subject: below --
2010-02-23 21:34 Daniel J Walsh
2010-03-05 18:47 ` Christopher J. PeBenito
2009-11-12 20:57 Daniel J Walsh
2009-05-21 15:15 Daniel J Walsh
2009-03-24 13:23 Daniel J Walsh
2009-03-02 22:27 Daniel J Walsh
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=4C0962D9.10300@redhat.com \
--to=dwalsh@redhat.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.