Re: default policy package

[Diyab <diyab@diyab.net>]

Russell Coker wrote:

> On Tue, 4 Nov 2003 00:38, Diyab wrote:
> 
>>I ran into a similar problem with postgresql.te which contains a
>>can_exec statement with dpkg_exec_t that does not have an ifdef around
>>it.  So unless you include dpkg.te you get an error attempting to
>>compile the policy.  Easiest thing to do from what I've found is to grep
>>the everything in domains/program for the context that is giving the error.
> 
> 
> I fixed that error some time ago.
> 
> One thing I have been considering is writing some scripts to check for such 
> errors.
> 
> My initial thought was to try compiling all combinations of packages.  But 
> that would involve hundreds of thousands of compilations.  So my current idea 
> is to m4 process each .te file with only the macro files and then search for 
> type declarations.  Then make a list of all .te files which reference those 
> types or attributes that they posess.  Then once the list of inter-dependence 
> between policy files is prepared it should be only a few hundred compilations 
> needed to prove that the policy will compile in all valid configurations.
> 

This is true.  I did not mean to imply that it had not been fixed but I 
did not specifically state that it had or had not, my apologies.

Timothy,

-- 
I put instant coffee in a microwave and almost went back in time.
		-- Steven Wright


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