All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmillan@mentalrootkit.com>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: ewalsh@tycho.nsa.gov, selinux@tycho.nsa.gov
Subject: Re: [PATCH 0/5] libselinux: labeling API for userspace object managers (try 2)
Date: Fri, 01 Dec 2006 12:04:59 -0500	[thread overview]
Message-ID: <457060BB.5090305@mentalrootkit.com> (raw)
In-Reply-To: <456F976D.9020905@tresys.com>

Joshua Brindle wrote:
> Eamon Walsh wrote:
>> This is a companion interface to the userspace AVC, for use by userspace
>> object managers to look up contexts for use in labeling their objects.
>> It also provides an alternate interface to the file contexts
>> configuration.
>>
>>   
> If we go forward with this do we really expect every object manager that 
> has context matching more complicated than exact matches to upstream 
> changes to libselinux? This doesn't seem to scale well.. Policy server 
> would need a backend, do you know if dbus and X would need new backends? 
> I still don't think this is the right approach, LDAP and rdbms's, for 
> example, would likely have their initial contexts in the schema.
> 

I agree that this would be problematic - very specific libselinux 
dependencies are going to be a nightmare for distributions. Seems like 
it should be possible to have a callback style api that would allow 
sufficient customization for almost all object managers.

> I can think of few object managers that this scheme works with. Things 
> like groupware apps, chat servers, mail servers, etc are going to have 
> labeling done at runtime (based on who creates an object or where it 
> comes from), databases will certainly store contexts in their schema, 
> etc. This is a pretty large change to make the file context interface a 
> little prettier..
> 

It this only works for file contexts then it doesn't seem worth doing, 
but I think that there is hope that it can be made to work more generally.

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:[~2006-12-01 17:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30  3:47 [PATCH 0/5] libselinux: labeling API for userspace object managers (try 2) Eamon Walsh
2006-11-30  4:05 ` [PATCH 1/5] libselinux: labeling API basic front-end interface Eamon Walsh
2006-12-06 17:15   ` Karl MacMillan
2006-11-30  4:08 ` [PATCH 2/5] libselinux: labeling API basic front-end implementation Eamon Walsh
2006-11-30  4:15 ` [PATCH 3/5] libselinux: class and av_perm to string functions Eamon Walsh
2006-11-30  4:19 ` [PATCH 4/5] libselinux: labeling API simple backend Eamon Walsh
2006-11-30  4:22 ` [PATCH 5/5] libselinux: labeling API file_contexts backend Eamon Walsh
2006-11-30 21:18 ` [PATCH] labeling API examples: setfiles patch and simple program Eamon Walsh
2006-12-01  2:46 ` [PATCH 0/5] libselinux: labeling API for userspace object managers (try 2) Joshua Brindle
2006-12-01 17:04   ` Karl MacMillan [this message]
2006-12-01 21:24     ` Eamon Walsh
2006-12-02  3:36       ` Joshua Brindle

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=457060BB.5090305@mentalrootkit.com \
    --to=kmacmillan@mentalrootkit.com \
    --cc=ewalsh@tycho.nsa.gov \
    --cc=jbrindle@tresys.com \
    --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.