From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: KaiGai Kohei <kaigai@kaigai.gr.jp>,
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: Mon, 12 Mar 2007 13:10:54 -0400 [thread overview]
Message-ID: <45F5899E.9070408@tycho.nsa.gov> (raw)
In-Reply-To: <1173458274.3241.122.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> Ok, you'll need to figure out the optimal approach there, as you need
> low runtime overhead for the actual permission checks. They would be
> changing from having the form:
> rc = avc_has_perm(ssid, tsid, SECCLASS_DATABASE,
> DATABASE__ACCESS, ...);
> to having a form like:
> rc = pgres_has_perm(ssid, tsid, PGRES_DATABASE_ACCESS, ...);
> where pgres_has_perm() could do something like:
> rc = index2policy(PGRES_DATABASE_ACCESS, &tclass, &perms);
> if (rc) return rc;
> rc = avc_has_perm(ssid, tsid, tclass, perms, ...);
>
> So you'd have a postgres-private index value for each distinct
> permission check it performs, mapped to a (class, perms) pair by the
> index2policy() function, using a lookup table generated once during
> startup from the string names using the libselinux functions (and
> revalidated upon policy reload notification).
If having an index2policy table is going to be a common usage model for
userspace object managers then perhaps support for it should be included
in libselinux.
--
Eamon Walsh <ewalsh@tycho.nsa.gov>
National Security Agency
--
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-12 17:10 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
2007-03-09 16:37 ` Stephen Smalley
2007-03-12 17:10 ` Eamon Walsh [this message]
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=45F5899E.9070408@tycho.nsa.gov \
--to=ewalsh@tycho.nsa.gov \
--cc=cpebenito@tresys.com \
--cc=csellers@tresys.com \
--cc=jbrindle@tresys.com \
--cc=kaigai@kaigai.gr.jp \
--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.