From: pebenito@gentoo.org (Chris PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] kernel_filesystem.patch
Date: Sat, 13 Mar 2010 18:38:08 -0500 [thread overview]
Message-ID: <1268523488.6161.2.camel@defiant> (raw)
In-Reply-To: <20100313181743.GA5024@localhost.localdomain>
On Sat, 2010-03-13 at 19:17 +0100, Dominick Grift wrote:
> in Fri, Mar 12, 2010 at 03:52:02PM -0500, Christopher J. PeBenito wrote:
> > On Fri, 2010-03-12 at 15:24 -0500, Daniel J Walsh wrote:
> > > On 03/12/2010 11:41 AM, Christopher J. PeBenito wrote:
> > > > On Tue, 2010-02-23 at 17:09 -0500, Daniel J Walsh wrote:
> > > >> devtmpfs file system
> > > >>
> > > > I'm thinking that perhaps devtmpfs should be moved to devices and use
> > > > device_t, since thats its only purpose.
> > > >
> > > >
> > > Sounds good to me.
> > >
> > > Will this work?
> > >
> > > fs_use_trans devtmpfs gen_context(system_u:object_r:device_t,s0);
> >
> > I don't have a system with devtmpfs, so I can't be sure, but I would
> > think it would work. That line would go in the devices module.
>
> Although we might get some of these:
>
> allow devlog_t device_t:filesystem associate;
> allow tty_device_t device_t:filesystem associate;
Thats easy enough to fix, just put this in devices.te:
allow device_node device_t:filesystem associate;
along with something similar in dev_filetrans(). Thanks for testing it
out.
--
Chris PeBenito
<pebenito@gentoo.org>
Developer,
Hardened Gentoo Linux
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243
Key fingerprint = B0E6 877A 883F A57A 8E6A CB00 BC8E E42D E6AF 9243
next prev parent reply other threads:[~2010-03-13 23:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 22:09 [refpolicy] kernel_filesystem.patch Daniel J Walsh
2010-03-12 16:41 ` Christopher J. PeBenito
2010-03-12 20:24 ` Daniel J Walsh
2010-03-12 20:52 ` Christopher J. PeBenito
2010-03-13 15:39 ` Dominick Grift
2010-03-13 18:17 ` Dominick Grift
2010-03-13 23:38 ` Chris PeBenito [this message]
2010-03-20 15:59 ` Dominick Grift
2010-03-22 13:49 ` Daniel J Walsh
-- strict thread matches above, loose matches on Subject: below --
2010-08-26 23:18 Daniel J Walsh
2010-06-02 20:23 Daniel J Walsh
2010-06-04 13:34 ` Christopher J. PeBenito
2010-06-04 13:41 ` Daniel J Walsh
2010-06-07 12:49 ` Christopher J. PeBenito
2010-06-07 12:57 ` Dominick Grift
2010-06-07 14:00 ` Christopher J. PeBenito
2010-06-07 14:17 ` Dominick Grift
2010-06-07 14:56 ` Christopher J. PeBenito
2010-06-07 15:24 ` Dominick Grift
2010-06-07 15:41 ` Christopher J. PeBenito
2010-06-07 16:50 ` Daniel J Walsh
2010-06-04 15:59 ` Dominick Grift
2009-11-12 21:02 Daniel J Walsh
2009-11-23 18:16 ` Christopher J. PeBenito
2009-05-21 15:26 Daniel J Walsh
2009-06-08 17:17 ` Christopher J. PeBenito
2009-03-02 22:20 Daniel J Walsh
2009-03-04 16:16 ` Christopher J. PeBenito
2008-11-25 21:45 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=1268523488.6161.2.camel@defiant \
--to=pebenito@gentoo.org \
--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.