From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: selinux@tycho.nsa.gov, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [ SEMANAGE ] Add a few direct dbases to handle
Date: Fri, 14 Oct 2005 16:40:18 -0400 [thread overview]
Message-ID: <435017B2.7040107@cornell.edu> (raw)
In-Reply-To: <4350131E.8060708@tresys.com>
> I thought we agreed to have a direct only accessible part of the
> handle, such as
>
> struct semanage_direct_handle {
> semanage_handle_t *handle;
> /* direct stuff goes here */
> };
I'm a little confused...
The dbase_config_t type is an a container for a database and its method
table, which together form an interface.
The interface does not specify implementation, so you can implement this
database differently using the policy server.
That patch also included code to init this database using the direct
"constructor" - when you call <something>_direct_dbase_init(). That part
was wrong, and if you look in the bugfix patch (#5), you will see that I
moved the direct-specific part into direct_api.h, to be invoked on
connect(), rather than create().
> So that this stuff is only exposed to direct api functions? The policy
> server shouldn't be filling out databases that are accessible to the
> user since it needs to mediate access.
I'm not sure I understand this.. s/"are"/"aren't"?
Note that those databases are needed regardless of backend - they're
specified using an interface.
--
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-10-14 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 18:16 [ SEMANAGE ] Add a few direct dbases to handle Ivan Gyurdiev
2005-10-14 18:39 ` [ SEMANAGE ] Bugfix previous patches Ivan Gyurdiev
2005-10-14 20:08 ` Stephen Smalley
2005-10-14 20:20 ` [ SEMANAGE ] Add a few direct dbases to handle Joshua Brindle
2005-10-14 20:40 ` Ivan Gyurdiev [this message]
2005-10-14 20:45 ` Ivan Gyurdiev
2005-10-14 20:39 ` Joshua Brindle
2005-10-14 20:59 ` Ivan Gyurdiev
2005-10-14 21:06 ` Joshua Brindle
2005-10-14 21:40 ` Ivan Gyurdiev
2005-10-15 11:34 ` Ivan Gyurdiev
2005-10-15 11:38 ` Ivan Gyurdiev
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=435017B2.7040107@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.