All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
	SELinux Mail List <selinux@tycho.nsa.gov>,
	Stephen Smalley <sds@tycho.nsa.gov>
Subject: RE: object class discovery userland
Date: Fri, 20 Apr 2007 10:17:53 -0400	[thread overview]
Message-ID: <1177078673.4625.1.camel@localhost.localdomain> (raw)
In-Reply-To: <6FE441CD9F0C0C479F2D88F959B01588A717F1@exchange.columbia.tresys.com>

On Fri, 2007-04-20 at 10:04 -0400, Joshua Brindle wrote:
> > From: Christopher J. PeBenito 
> > 
> > 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 started looking at the userland side of this, 
> > and there are some relevant
> > functions:
> > 
> > security_class_t string_to_security_class(const char *name); 
> > const char *security_class_to_string(security_class_t cls);
> > 
> > access_vector_t string_to_av_perm(security_class_t tclass, 
> > const char *name); const char 
> > *security_av_perm_to_string(security_class_t tclass, 
> > access_vector_t perm);
> > 
> > The implementation for the first one is straightforward, just 
> > look at the index file for the class.  The other three are a 
> > little more problematic with the above structure since they 
> > use an index, since it would have to search through the 
> > CLASSNAME/index files to find the right one.
> > 
> > So to get the reverse lookup we could:
> > 1. search /selinux/class/ in the userland code 2. create 
> > symlinks /selinux/class, one possible structure:
> > 
> > /selinux/class/1 -> security
> > /selinux/class/2 -> process
> > /selinux/class/security/perms/1 -> compute_av
> > /selinux/class/security/perms/2 -> compute_create
> > 
> > 3. stop exporting class and perm indexes outside of the 
> > libraries.  Then the reverse lookup wouldn't be needed.  This 
> > would involve some overhauling of the libraries.
> > 
> > 4. other ideas?
> > 
> 
> I think we should do the symlink thing to support the current interfaces
> but mark them as deprecated and implement a new string based API. Then
> work on getting all the object managers switched over to the string API
> and eventually deprecate the userspace side and remove the symlinks.
> 

If it is deprecated then why do the symlinks? It is only an optimization
and libselinux can cache the mappings after the first lookup. The
symlinks also complicate the code to do string lookup (because they have
to ignore the numeric nodes).

Karl


--
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 14:17 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 [this message]
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
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=1177078673.4625.1.camel@localhost.localdomain \
    --to=kmacmillan@mentalrootkit.com \
    --cc=cpebenito@tresys.com \
    --cc=jbrindle@tresys.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.