From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: [ SEPOL/SEMANAGE ] Boolean record
Date: Tue, 20 Sep 2005 15:35:43 -0400 [thread overview]
Message-ID: <4330648F.7040609@cornell.edu> (raw)
In-Reply-To: <1127243186.14569.135.camel@moss-spartans.epoch.ncsc.mil>
>How useful is it to wrap these libsepol interfaces with libsemanage?
>
>
What do you mean?
The alternative is to either:
- implement the same interfaces in both places (which is worse), or
- have semanage functions take sepol data stuctures as arguments (which
is bad design practice).
I don't think the current scheme is too bad - esp. because the wrap
functions are inlined.
--
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 19:35 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 [this message]
2005-09-20 19:56 ` Stephen Smalley
2005-09-20 20:16 ` Ivan Gyurdiev
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=4330648F.7040609@cornell.edu \
--to=ivg2@cornell.edu \
--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.