All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: KaiGai Kohei <kaigai@kaigai.gr.jp>
Cc: SELinux Mail List <selinux@tycho.nsa.gov>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Joshua Brindle <jbrindle@tresys.com>
Subject: Re: object class discovery userland
Date: Fri, 20 Apr 2007 11:32:14 -0400	[thread overview]
Message-ID: <1177083134.24870.9.camel@sgc> (raw)
In-Reply-To: <4628D4FE.5050604@kaigai.gr.jp>

On Fri, 2007-04-20 at 23:58 +0900, KaiGai Kohei wrote:
> Christopher J. PeBenito wrote:
> > I have nearly completed the kernel patch for object class discovery
> > which creates the structure:
> > 
> > /selinux/class/CLASSNAME/index
> > /selinux/class/CLASSNAME/perms/PERMNAME
> > 
> > so you get the class index number from the index file, and the
> > permission name file gets the index number of the permission.

> I really wanted the kernel/userland interface to obtain object classes and
> permissions number.
> 
> BTW, what is the reason for 1:1 mapping between PERMNAME entry and permission number?
> For example, if /selinux/class/index provides the pair of object class number/name
> and /selinux/class/CLASSNAME provides the pair of permission number/name, we can
> obtain them with simple iterations of fscanf("%u %s", ...).

See http://marc.info/?l=selinux&m=117580309612610&w=2

> We maybe cache them in userland until the security policy reloaded.

Class and permission indexes aren't really used outside of userspace
object managers.  I'd expect object managers to do this for the classes
they care about, for themselves.

-- 
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150


--
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.

  reply	other threads:[~2007-04-20 15:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20 14:01 object class discovery userland Christopher J. PeBenito
2007-04-20 14:04 ` Joshua Brindle
2007-04-20 14:17   ` Karl MacMillan
2007-04-20 14:23     ` Joshua Brindle
2007-04-20 14:22       ` Karl MacMillan
2007-04-20 14:27         ` Joshua Brindle
2007-04-20 14:58 ` KaiGai Kohei
2007-04-20 15:32   ` Christopher J. PeBenito [this message]
2007-04-20 16:54 ` Eamon Walsh
2007-04-20 17:02   ` Eamon Walsh
2007-04-20 17:19     ` Christopher J. PeBenito
2007-04-23 14:33       ` Stephen Smalley
2007-04-23 14:43         ` Joshua Brindle
2007-04-23 14:58           ` Stephen Smalley
2007-05-23 14:17             ` Christopher J. PeBenito
2007-05-23 18:51               ` Eamon Walsh
2007-05-24 23:46                 ` Eamon Walsh
2007-05-24 23:55                   ` Joshua Brindle
2007-05-25  0:00                   ` Joshua Brindle
2007-05-25 21:10                     ` Eamon Walsh
2007-05-25 22:36                       ` Joshua Brindle
2007-05-29 17:50                         ` Eamon Walsh
2007-05-29 18:36                           ` Stephen Smalley
2007-05-29 18:24                       ` Stephen Smalley
2007-05-29 19:17                         ` Eamon Walsh
2007-05-30  2:20                       ` KaiGai Kohei
2007-05-30 20:01                         ` Eamon Walsh
2007-05-31 13:28                           ` KaiGai Kohei
2007-06-01 17:18                             ` Eamon Walsh
2007-05-29 18:19               ` Stephen Smalley
2007-05-29 19:06                 ` Eamon Walsh
  -- strict thread matches above, loose matches on Subject: below --
2007-04-23 16:33 Nick Nam
2007-04-23 16:36 Nick Nam

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=1177083134.24870.9.camel@sgc \
    --to=cpebenito@tresys.com \
    --cc=jbrindle@tresys.com \
    --cc=kaigai@kaigai.gr.jp \
    --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.