From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Ivan Gyurdiev <ivg2@cornell.edu>, selinux@tycho.nsa.gov
Subject: Re: [ SEMANAGE ] Cleanup : move some things around
Date: Mon, 07 Nov 2005 11:30:20 -0500 [thread overview]
Message-ID: <436F811C.1010306@tresys.com> (raw)
In-Reply-To: <1131379914.20591.70.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
> On Mon, 2005-11-07 at 11:22 -0500, Ivan Gyurdiev wrote:
>
>>>I'd prefer to hold cleanups until we have stabilized the functionality
>>>and interfaces as desired for test1. I'm also not clear on why we want
>>>a sepol handle in the ps case.
>>>
>>
>>.. because we'll be using the sepol records either way, so we need the
>>sepol handle..
>>Not using the sepol records requires copying them over into libsemanage.
>
>
> Hmmm..well, let's take that up again later. Right now we need to deal
> with finalizing the boolean support (e.g. having libsemanage use
> security_set_boolean_list with permanent=0 to set the runtime boolean
> values upon commit rather than loading the generated binary policy
> file), and getting the migration steps in place for test1.
>
> I committed your semanage_set_reload_bools() patch and my
> semanage_is_managed() patch to sourceforge cvs, but not the cleanup
> patch.
>
Please see my other email about the semanage_set_reload_bools() patch, I
believe it is flawed in a couple ways and should be reverted.
Joshua
--
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-11-07 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 10:30 [ SEMANAGE ] Cleanup : move some things around Ivan Gyurdiev
2005-11-07 15:33 ` Stephen Smalley
2005-11-07 16:22 ` Ivan Gyurdiev
2005-11-07 16:11 ` Stephen Smalley
2005-11-07 16:30 ` Joshua Brindle [this message]
2005-11-07 16:31 ` Stephen Smalley
2005-11-07 16:46 ` 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=436F811C.1010306@tresys.com \
--to=jbrindle@tresys.com \
--cc=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.