From: Joshua Brindle <jbrindle@tresys.com>
To: ewalsh@tycho.nsa.gov
Cc: selinux@tycho.nsa.gov, sds@tycho.nsa.gov
Subject: Re: [PATCH 0/5] libselinux: labeling API for userspace object managers
Date: Thu, 16 Nov 2006 09:10:05 -0500 [thread overview]
Message-ID: <455C713D.9050104@tresys.com> (raw)
In-Reply-To: <1163643926.15225.55.camel@moss-huskies.epoch.ncsc.mil>
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.
>
> The need for this interface is discussed in this thread:
> http://marc.theaimsgroup.com/?l=selinux&m=116195833329572&w=2
>
> The interface provides support for pluggable backends, multithreading,
> and user-provided callbacks for logging, memory allocation, and context
> validation. It is designed to allow policy separation by package (the
> "prefix" string). Lookups are done by object class and a string "key".
>
>
I didn't think this was a solved problem. I still think labeling is part
of the object manager, not part of the policy. What are the advantages
of doing it this way over letting the object managers manage their own
labels?
about this implementation though, how are you planning to get contexts
to the policy directory? As part of a package? any libsemanage
interface? Will it be part of this patch set?
Did you need a special backend for file_contexts because it has
overlapping object class specifications? How do you 'register' an object
class or set of object classes to a particular backend? I know with X
you are going to have 1 file with many object classes, will it need a
special backend? If every single object manager needs a special backend
what are we buying with this interface?
I assume this is for RFC and not for merging until the rest of the
patches are out, right? If you could make the patches apply from the top
of the repository with -p0 or -p1 (don't have a preference which) that
would be really helpful.
--
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:[~2006-11-16 14:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 2:25 [PATCH 0/5] libselinux: labeling API for userspace object managers Eamon Walsh
2006-11-16 2:46 ` [PATCH 1/5] libselinux: labeling API basic front-end interface Eamon Walsh
2006-11-20 15:36 ` Karl MacMillan
2006-11-27 22:23 ` Eamon Walsh
2006-11-16 2:51 ` [PATCH 2/5] libselinux: labeling API basic front-end implementation Eamon Walsh
2006-11-20 15:42 ` Karl MacMillan
2006-11-27 22:44 ` Eamon Walsh
2006-11-16 14:10 ` Joshua Brindle [this message]
2006-11-16 18:49 ` [PATCH 0/5] libselinux: labeling API for userspace object managers Eamon Walsh
2006-11-16 19:06 ` [PATCH 0/5] libselinux: labeling API for userspace objectmanagers Joshua Brindle
2006-11-16 21:12 ` Eamon Walsh
2006-11-16 21:54 ` [PATCH 3/5] libselinux: security_class_to_string helper function Eamon Walsh
2006-11-18 1:05 ` KaiGai Kohei
2006-11-27 22:45 ` Eamon Walsh
2006-11-16 22:55 ` [PATCH 4/5] libselinux: labeling API simple backend Eamon Walsh
2006-11-17 23:09 ` [PATCH 5/5] libselinux: labeling API file_contexts backend Eamon Walsh
2006-11-18 0:46 ` [PATCH 0/5] libselinux: one large patch Eamon Walsh
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=455C713D.9050104@tresys.com \
--to=jbrindle@tresys.com \
--cc=ewalsh@tycho.nsa.gov \
--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.