From: Joshua Brindle <method@manicmethod.com>
To: Keith Holder <keith_holder@symantec.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: non-standard filesystem support in SELinux
Date: Tue, 15 May 2007 07:34:14 -0400 [thread overview]
Message-ID: <46499AB6.2070109@manicmethod.com> (raw)
In-Reply-To: <46499808.9030001@symantec.com>
Keith Holder wrote:
> Joshua Brindle wrote:
>> Keith Holder wrote:
>>>
>>> A quick question on loadable policy modules.
>>>
>>> Are there any plans to allow 3rd party filesystem support,
>>> without having to edit/recompile the base policy module?
>>>
>>> keith
>>
>> I don't think we've ever thought about it, it seems like something
>> that is very uncommon. I suppose its something we could do when we
>> rewrite the compiler to use the new representation but it won't be
>> high on the list of priorities. To be clear, what kind of support are
>> you looking for? fs_use_* support or genfs support?
>
> Mostly fs_use_* so that the filesystem, mount points and
> underlying files don't end up with the unlabeled_t type as
> the default.
>
Is there a reason you can't use the context mount option to label the
mountpoint and its underlying files?
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2007-05-15 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 22:14 [ANN] SELinux kernel project page James Morris
2007-05-11 22:54 ` Serge E. Hallyn
2007-05-11 23:06 ` Karl MacMillan
2007-05-15 9:33 ` non-standard filesystem support in SELinux Keith Holder
2007-05-15 11:14 ` Joshua Brindle
2007-05-15 11:22 ` Keith Holder
2007-05-15 11:34 ` Joshua Brindle [this message]
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=46499AB6.2070109@manicmethod.com \
--to=method@manicmethod.com \
--cc=keith_holder@symantec.com \
--cc=selinux@tycho.nsa.gov \
/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.