All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eamon Walsh <ewalsh@tycho.nsa.gov>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: object class discovery userland
Date: Tue, 29 May 2007 13:50:35 -0400	[thread overview]
Message-ID: <465C67EB.1040801@tycho.nsa.gov> (raw)
In-Reply-To: <6FE441CD9F0C0C479F2D88F959B01588BEFFA2@exchange.columbia.tresys.com>

Joshua Brindle wrote:
> Eamon Walsh wrote:
>> Here's a first go at an interface.  It's an init function
>> that is a replacement for avc_init().  It takes flags, the
>> class/permission mapping to use, and callback functions.
>>
>> This is trying to solve a few other problems at the same time, namely:
>>
>> - selinux prefix on the function name
> 
> So the client callsites will have to change then, oh well, we wanted to
> do this anyway..

Well, the old avc_init() could be kept around for awhile.  Calling it 
would still work, it just wouldn't have a mapping (would treat incoming 
class/perm values literally).

> 
>> - drops support for memory, threading, and locking callbacks
>> (would just always use malloc and pthread)
> 
> Were these ever used or were they a remnant of the early
> implementations?

I'm not aware of any users of them.  I put them in basically because the 
X server wrapped malloc ("Xalloc"), glib has malloc wrappers and so 
forth.  But the X people are moving away from this and back to straight 
malloc.  I've come around to the belief that this is better done through 
the linker with private functions.


>> - adds type code to logging callback
>>
>> ---
>>
>>  selinux.h |   37 +++++++++++++++++++++++++++++++++++++
>>  1 file changed, 37 insertions(+)
>>
>>
>> Index: libselinux/include/selinux/selinux.h
>> ===================================================================
>> --- libselinux/include/selinux/selinux.h	(revision 2445)
>> +++ libselinux/include/selinux/selinux.h	(working copy) @@ -132,6
>>  		+132,43 @@ unsigned int seqno;
>>  	};
>>
>> +	struct av_mapping {
>> +		const char *name;
>> +		const access_vector_t value;
>> +	};
>> +
> 
> Should this be a linked list?

I was thinking that the last element could be zeroed out.  Same thing 
with the last class element.  Would make it easier to have a static 
initializer e.g.

struct security_class_mapping *mapping = {
	{ "xwindow", 32, {{"create", 1}, {"draw", 2}, {NULL, 0}} },
	{ "xcursor", 33, {{"create", 1}, {"show", 2}, {NULL, 0}} },
	{ NULL, 0, NULL }
};


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

  reply	other threads:[~2007-05-29 17:50 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
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 [this message]
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=465C67EB.1040801@tycho.nsa.gov \
    --to=ewalsh@tycho.nsa.gov \
    --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.