Re: More small fixes to policycoreutils

[Joshua Brindle <jbrindle@tresys.com>]

Stephen Smalley wrote:
> On Mon, 2006-11-20 at 15:14 -0500, Karl MacMillan wrote:
>> Joshua Brindle wrote:
>>> Its interesting that semanage manages something that is redhat specific 
>>> and not part of the upstream utilities at all.. IMO this should never 
>>> have been merged in the first place, semanage manages libsemanage 
>>> abstractions, if translations were a part of libsemanage it'd be a 
>>> different story.
>>>
>> Why isn't setrans upstream?
> 
> It wasn't clear that there was any demand for it outside of Fedora /
> RHEL, and it was always optional.  If other distros are going to use it
> (e.g. Debian?), then I agree it should likely be added (after code
> review and cleanup, of course).
> 

Also, is this server only for mcs? Does MLS/LSPP config use a different 
server? It seems like this needs to be more general that mcs, since that 
doesn't really mean anything anyway.

>>>> @@ -204,7 +206,8 @@
>>>>          os.write(fd, self.out())
>>>>          os.close(fd)
>>>>          os.rename(newfilename, self.filename)
>>>> -
>>>> +                os.system("/sbin/service mcstrans reload > /dev/null")
>>>> +                
>>> This is very distro specific and totally inappropriate IMO.
>>>
>> Agreed - what is the solution, though?
> 
> Configurable pre and post scriptlets, defined externally and optional?
> 

Same question as above, does semanage management of translations break 
down on MLS configs? If so I'd vote for all this code to be ripped out 
of semanage altogether and put into another tool that is specific to the 
  mcstrans server, since the translation file is server specific anyway.


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