Re: libsetrans and libselinux

[Daniel J Walsh <dwalsh@redhat.com>]

Stephen Smalley wrote:
> On Tue, 2006-01-03 at 00:55 -0500, Joshua Brindle wrote:
>   
>> The only users of libsetrans are ones that use context functions in 
>> libselinux, and several apps that link to libselinux but don't use those 
>> (such as load_policy, init, etc)
>>
>> Further, IIRC libsetrans is being maintained by RH and is not in the nsa 
>> mainline cvs tree. And as Dan was saying, the whole reason for 
>> libsetrans to begin with was for drop in translation libraries (such as 
>> Mitre's)
>>     
>
> Yes, Dan earlier proposed integrating libsetrans into libselinux IIRC,
> and I resisted.  However, if libsetrans were made suitably generic such
> that it wouldn't need to be replaced entirely in order to support things
> like the MITRE library, then it might be reasonable to fold it into
> libselinux.  It is true that subtle bugs and memory leaks can crop up
> now due to the separation.
>
>   
There has been some thought to making it daemon based.  And allow 
libsetrans setup a
unix_domain_socket to talk across.  This would allow us to implement a 
daemon and eliminate
the reprocessing of the file each time an application starts.  Then you 
could just replace the daemon.
> MITRE also thought it possible that their translation library could be
> open sourced, if that would help.  Not sure how long it would take to
> gain approval though...
>
>   
I thought there might be classification problems in there also?

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