From: Paul Moore <paul.moore@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: Query MLS info outside of SELinux/LSM?
Date: Fri, 10 Mar 2006 12:22:58 -0500 [thread overview]
Message-ID: <4411B5F2.6060702@hp.com> (raw)
In-Reply-To: <1142010664.25454.128.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Fri, 2006-03-10 at 11:56 -0500, Paul Moore wrote:
>
>>Is there a way to query the number of MLS sensitivity levels and
>>categories outside of the SELinux LSM? I haven't seen anything, but
>>thought I would ask before I started looking at alternatives ... which
>>brings me to my next question - would anyone have an objection to adding
>>this functionality?
>
> The goal is to keep information about the specific security models
> encapsulated in the security server (security/selinux/ss/*.c). The rest
> of the SELinux code then remains policy-independent, as does the rest of
> the kernel.
>
The only concern I have with the above statement is that in some cases,
i.e. labeled networking, some of that security model information such as
MLS limits is important outside the security server.
--
paul moore
linux security @ hp
--
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.
next prev parent reply other threads:[~2006-03-10 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 16:56 Query MLS info outside of SELinux/LSM? Paul Moore
2006-03-10 17:11 ` Stephen Smalley
2006-03-10 17:22 ` Paul Moore [this message]
2006-03-10 17:37 ` Stephen Smalley
2006-03-10 17:38 ` Paul Moore
2006-03-10 17:53 ` Stephen Smalley
2006-03-10 19:03 ` Joe Nall
2006-03-10 19:15 ` Stephen Smalley
2006-03-10 19:16 ` Paul Moore
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=4411B5F2.6060702@hp.com \
--to=paul.moore@hp.com \
--cc=sds@tycho.nsa.gov \
--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.