From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Karl MacMillan <kmacmillan@tresys.com>
Cc: selinux@tycho.nsa.gov, "'Joshua Brindle'" <jbrindle@tresys.com>
Subject: Re: [PATCH] semanage-functionality 4/17
Date: Tue, 27 Sep 2005 12:54:56 -0400 [thread overview]
Message-ID: <43397960.5070905@cornell.edu> (raw)
In-Reply-To: <200509271246.j8RCkcYs026042@gotham.columbia.tresys.com>
\Karl MacMillan wrote:
>This patch adds semanage.h - this is the new public interface for
>libsemanage.
>
>
Why is it that you have to keep re-adding the components that I'm
currently working on. Please leave those out of the semanage.h header
for now. If you don't approve of my APIs, then you should submit patches
on top of them, instead of introducing duplicate work. Anything that
says semanage_mls_* semanage_user_*, semanage_boolean_*, and
semanage_homedir_* should be left out for now.
1) Users - those will be handled via the user_record data structure,
which is already in CVS. The implementation is in sepol, but I've
uninlined the data structure, so the API is now opaque.
2) Booleans - those will be handle via the boolean_record data
structure. I have no included that in semanage yet, because I'm still
testing how other records (like the user record) will work, but you can
look at the data structure in sepol.
3) Homedirs - this part of the API is too unclear to add at this point
(at least, it's not clear to me yet, and I'll probably be implementing it..)
P.S. Your semanage header should likely draw in my user/port/record
headers, but please don't do this yet, as those interfaces are in flux.
Also, I think the handle stuff and the module stuff should go into
separate headers, and you should include those into semanage.h.
--
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:[~2005-09-27 16:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 12:46 [PATCH] semanage-functionality 4/17 Karl MacMillan
2005-09-27 16:54 ` Ivan Gyurdiev [this message]
2005-09-27 20:08 ` Stephen Smalley
2005-09-27 20:48 ` Ivan Gyurdiev
2005-09-27 20:57 ` Stephen Smalley
2005-09-30 13:02 ` Ivan Gyurdiev
2005-09-30 13:47 ` Karl MacMillan
2005-09-28 15:21 ` Karl MacMillan
2005-09-27 20:38 ` Karl MacMillan
2005-09-27 21:06 ` Ivan Gyurdiev
2005-09-27 21:10 ` Stephen Smalley
2005-09-28 15:15 ` Karl MacMillan
2005-09-28 14:52 ` Stephen Smalley
2005-09-28 15:21 ` Ivan Gyurdiev
2005-09-28 15:33 ` Karl MacMillan
2005-09-28 15:31 ` Karl MacMillan
2005-09-28 15:59 ` Stephen Smalley
2005-09-28 16:24 ` Karl MacMillan
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=43397960.5070905@cornell.edu \
--to=ivg2@cornell.edu \
--cc=jbrindle@tresys.com \
--cc=kmacmillan@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.