From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] kernel_storage.patch
Date: Tue, 09 Jun 2009 06:33:09 -0400 [thread overview]
Message-ID: <4A2E3A65.4090801@redhat.com> (raw)
In-Reply-To: <1244481472.21565.454.camel@gorn>
On 06/08/2009 01:17 PM, Christopher J. PeBenito wrote:
> On Thu, 2009-05-21 at 11:28 -0400, Daniel J Walsh wrote:
>> http://people.fedoraproject.org/~dwalsh/SELinux/F11/kernel_storage.patch
>>
>> /dev/fuse should be s0 not mls_high
>
>> From my understanding of the FUSE website, the data from the userland FS
> is transferred through this device. Since the data may go up to system
> high, I believe the device should still be system high.
>
Making it systemhigh will generate lots of AVC messages on every login
at X Since fusefs is mounted at ~/.gfs. It will also make it unusable I
believe on an MLS machine. Mostly I have seen fusefs used for remote
access to data. sshfs for example.
next prev parent reply other threads:[~2009-06-09 10:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 15:28 [refpolicy] kernel_storage.patch Daniel J Walsh
2009-06-08 17:17 ` Christopher J. PeBenito
2009-06-09 10:33 ` Daniel J Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-26 23:20 Daniel J Walsh
2010-06-02 20:26 Daniel J Walsh
2010-06-04 13:44 ` Christopher J. PeBenito
2010-02-23 19:36 Daniel J Walsh
2010-03-04 19:23 ` Christopher J. PeBenito
2010-03-05 16:05 ` Daniel J Walsh
2010-03-05 16:06 ` Daniel J Walsh
2010-03-05 16:09 ` Christopher J. PeBenito
2009-11-12 21:04 Daniel J Walsh
2009-11-19 14:03 ` Christopher J. PeBenito
2009-11-19 14:19 ` Daniel J Walsh
2009-11-19 14:51 ` Christopher J. PeBenito
2009-03-04 21:33 Daniel J Walsh
2009-03-05 16:12 ` Christopher J. PeBenito
2009-03-05 17:28 ` Daniel J Walsh
2009-03-05 18:18 ` Christopher J. PeBenito
2009-03-05 19:17 ` Daniel J Walsh
2008-11-25 21:51 Daniel J Walsh
2008-09-24 20:52 Daniel J Walsh
2008-10-06 17:31 ` Christopher J. PeBenito
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=4A2E3A65.4090801@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.