[apparmor] environment variables

John Johansen john.johansen at canonical.com
Tue Nov 8 23:24:27 UTC 2011


On 11/08/2011 02:20 PM, Kees Cook wrote:

So one more thing that I meant to ask in my previous reply

> I think this is good to finally address. I mean, even just looking at
> the execve() call itself, it takes path, args, and env. It wouldn't be
> totally crazy to extend the matching to include env in the matching.
> 
> On Mon, Nov 07, 2011 at 11:13:49PM -0800, John Johansen wrote:
>> 2. Environment filtering
>>
>> Environment filtering would be like extending the existing secure exec, except
>> with policy involvement, so the environment variable filtering could be defined
>> per rule or profile.
>>
>> It has many of the same questions as Matching.
>>
>> 2a. Should environment variable filtering be on the rule, profile or both?
> 
> It seems like "both" would be the place to do it.
> 

Interesting, would you envision them being applied together, or as an intersection.
ie.  Do the profile and file rules accumulate to increase the set of environment
vars that are passed, or do they intersect reducing the set.



More information about the AppArmor mailing list