From: KaiGai Kohei <kaigai@kaigai.gr.jp>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Eamon Walsh <ewalsh@tycho.nsa.gov>,
Joshua Brindle <jbrindle@tresys.com>,
"Christopher J. PeBenito" <cpebenito@tresys.com>,
selinux@tycho.nsa.gov, Chad Sellers <csellers@tresys.com>,
Karl MacMillan <kmacmillan@mentalrootkit.com>
Subject: Re: [ANN] SE-PostgreSQL 8.2.3-1.0 alpha release
Date: Sat, 10 Mar 2007 00:25:36 +0900 [thread overview]
Message-ID: <45F17C70.70707@kaigai.gr.jp> (raw)
In-Reply-To: <1173385436.3241.54.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Thu, 2007-03-08 at 11:24 -0500, Eamon Walsh wrote:
>> Stephen Smalley wrote:
>>
>>> There are already string_to_security_class() and string_to_av_perm()
>>> functions provided by libselinux, although they should likely have
>>> properly namespaced versions (selinux_ prefix).
>> If we're talking about the API in this area: I had a request for
>> security_class_to_string and av_perm_to_string functions, I believe from
>> KaiGai. The patch in the below e-mail adds them; this could be applied
>> as an independent patch.
>>
>> http://marc.theaimsgroup.com/?l=selinux&m=116486019626891&w=2
>
> Ok, so we could:
> - introduce new versions of the existing string_to_* functions with a
> security_ or selinux_ prefix for namespace cleanliness,
> - merge that patch, using the same convention for naming (either as is
> with security_ or replacing with selinux_,
> - have KaiGai rewrite his code to use these functions to map class and
> permission strings to policy values during startup of SEPostgreSQL,
> generating lookup tables for later use by the actual permission checks
> (where the lookup tables would map internal indices private to
> SEPostgreSQL to the policy-defined values obtained from libselinux).
> The tables would need to be revalidated and potentially refreshed upon a
> policy reload, which could be done from an AVC callback.
>
> Then SEPostgreSQL no longer needs to be compile-time bound to specific
> policy values for its classes and permissions.
I also think it's an excellent idea!
I'll rewrite a part of implementation to generate classes/access vectors
lookup table and to use them.
> Same could be done for XSELinux, right?
>
> Then when we have the dynamic discovery mechanism implemented, it can
> just be used by those libselinux functions internally, with no further
> change to the object managers.
--
KaiGai Kohei <kaigai@kaigai.gr.jp>
--
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:[~2007-03-09 15:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 12:29 [ANN] SE-PostgreSQL 8.2.3-1.0 alpha release KaiGai Kohei
2007-03-05 14:41 ` KaiGai Kohei
2007-03-07 16:17 ` Christopher J. PeBenito
2007-03-08 13:33 ` KaiGai Kohei
2007-03-08 13:33 ` Stephen Smalley
2007-03-08 14:50 ` KaiGai Kohei
2007-03-08 15:00 ` Stephen Smalley
2007-03-08 15:21 ` Joshua Brindle
2007-03-08 15:23 ` Joshua Brindle
2007-03-08 15:30 ` Stephen Smalley
2007-03-08 16:24 ` Eamon Walsh
2007-03-08 20:23 ` Stephen Smalley
2007-03-09 15:25 ` KaiGai Kohei [this message]
2007-03-09 16:37 ` Stephen Smalley
2007-03-12 17:10 ` Eamon Walsh
2007-03-12 17:50 ` Stephen Smalley
2007-03-08 17:30 ` Solaris 10 w/ Trusted Extensions vs SE Linux Comparison Fletcher, Boyd C. CIV US USJFCOM JFL J9935
2007-03-08 18:39 ` Fletcher, Boyd C. CIV US USJFCOM JFL J9935
2007-03-29 15:57 ` Karl MacMillan
2007-03-06 9:34 ` [ANN] SE-PostgreSQL 8.2.3-1.0 alpha release Russell Coker
2007-03-06 19:05 ` KaiGai Kohei
2007-03-06 19:17 ` Stephen Smalley
2007-03-06 22:36 ` Russell Coker
2007-03-07 14:01 ` KaiGai Kohei
2007-03-07 13:17 ` KaiGai Kohei
2007-03-07 14:58 ` Casey Schaufler
2007-03-07 15:58 ` James W. Hoeft
2007-03-07 16:01 ` Joshua Brindle
2007-03-08 13:12 ` KaiGai Kohei
2007-03-08 13:25 ` Stephen Smalley
2007-03-08 14:34 ` KaiGai Kohei
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=45F17C70.70707@kaigai.gr.jp \
--to=kaigai@kaigai.gr.jp \
--cc=cpebenito@tresys.com \
--cc=csellers@tresys.com \
--cc=ewalsh@tycho.nsa.gov \
--cc=jbrindle@tresys.com \
--cc=kmacmillan@mentalrootkit.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.