Re: [ SEMANAGE ] Cleanup : move some things around

[Ivan Gyurdiev <ivg2@cornell.edu>]

>>> 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.
>   
That's fine, but consider that when you call semanage records function 
before connect, or after disconnect with the semanage handle, your 
messages will go to stdout (since sepolh is NULL).

--
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.