From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: SELinux List <SELinux@tycho.nsa.gov>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [SEMANAGE] Commit numbers for ro database calls
Date: Mon, 02 Jan 2006 12:17:51 -0500 [thread overview]
Message-ID: <43B9603F.7060202@cornell.edu> (raw)
In-Reply-To: <43B97ACC.5080203@tresys.com>
>>
>> How is it broken? How should it read the data?
>>
> It should request the data from semanage_store if it is being stored
> in the store, just like you'd request the data from an LDAP server,
> etc. Right now the database is sneaking into the store without going
> through the store API, which is broken but like I said, probably not
> worth the time to fix.
I didn't realize there was an API for reading things from the store.
I guess what you're asking me to do is to move code for read/write into
the semanage_store,
which I could do, but I'm not sure I see the benefit of that - it will
just complicate things and make
the store dependent on polymorphism, which I'm guessing you wouldn't like.
--
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-01-02 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 11:28 [SEMANAGE] Commit numbers for ro database calls Ivan Gyurdiev
2006-01-02 18:44 ` Joshua Brindle
2006-01-02 16:56 ` Ivan Gyurdiev
2006-01-02 19:11 ` Joshua Brindle
2006-01-02 17:17 ` Ivan Gyurdiev [this message]
2006-01-02 19:20 ` Joshua Brindle
2006-01-03 20:39 ` 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=43B9603F.7060202@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux@tycho.nsa.gov \
--cc=jbrindle@tresys.com \
--cc=sds@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.