From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov, jbrindle@tresys.com
Subject: Re: [ SEPOL/SEMANAGE ] Boolean record
Date: Tue, 20 Sep 2005 16:16:29 -0400 [thread overview]
Message-ID: <43306E1D.2070508@cornell.edu> (raw)
In-Reply-To: <1127246178.14569.143.camel@moss-spartans.epoch.ncsc.mil>
>- keep the shared libsepol, and have applications use its interfaces
>directly.
>
To clarify, are you saying that we should have?
semanage_user_add(semanage_handle_t handle, sepol_user_key_t key,
sepol_user_t data)
semanage_user_del(semanage_handle_t handle, sepol_user_key_t key)
semanage_user_modify(semanage_handle_t handle, sepol_user_t key,
sepol_user_t data)
The sepol and semanage functionality is different - it's just the data
structure that's shared.
>That's what makes it seem so pointless. If the wrap functions weren't
>inlined and actually added some semantics around the libsepol
>implementation, then they might make sense
>
>
I don't know - it's just a design thing to allow future change - Joshua?
I'm not sure if the wrap functions add value, but at least they don't
cause any harm.
--
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-20 20:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 7:40 [ SEPOL/SEMANAGE ] Boolean record Ivan Gyurdiev
2005-09-20 19:06 ` Stephen Smalley
2005-09-20 19:35 ` Ivan Gyurdiev
2005-09-20 19:56 ` Stephen Smalley
2005-09-20 20:16 ` Ivan Gyurdiev [this message]
2005-09-20 20:22 ` Stephen Smalley
2005-09-20 20:48 ` Karl MacMillan
2005-09-20 21:07 ` Ivan Gyurdiev
2005-09-21 14:21 ` Stephen Smalley
2005-09-21 16:14 ` Ivan Gyurdiev
2005-09-20 21:42 ` Ivan Gyurdiev
2005-09-21 14:35 ` Stephen Smalley
2005-09-21 17:48 ` Karl MacMillan
2005-09-21 17:51 ` Stephen Smalley
2005-09-21 17:53 ` Stephen Smalley
2005-09-21 18:03 ` Karl MacMillan
2005-09-21 18:37 ` Ivan Gyurdiev
2005-09-21 18:33 ` Karl MacMillan
2005-09-22 1:50 ` Ivan Gyurdiev
2005-09-23 12:34 ` Karl MacMillan
2005-09-20 20:45 ` [ SEPOL ] Fix memory leaks Ivan Gyurdiev
2005-09-21 14:44 ` Stephen Smalley
2005-09-21 14:41 ` [ SEPOL/SEMANAGE ] Boolean record Stephen Smalley
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=43306E1D.2070508@cornell.edu \
--to=ivg2@cornell.edu \
--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.