[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <73a82dff7be151298f51c0db6f3c4996ccf44a19.camel@linux.ibm.com>
Date: Wed, 13 Jan 2021 21:09:23 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Tushar Sugandhi <tusharsu@...ux.microsoft.com>,
stephen.smalley.work@...il.com, casey@...aufler-ca.com,
agk@...hat.com, snitzer@...hat.com, gmazyland@...il.com,
paul@...l-moore.com
Cc: tyhicks@...ux.microsoft.com, sashal@...nel.org, jmorris@...ei.org,
nramas@...ux.microsoft.com, linux-integrity@...r.kernel.org,
selinux@...r.kernel.org, linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, dm-devel@...hat.com
Subject: Re: [PATCH v10 5/8] IMA: limit critical data measurement based on a
label
On Thu, 2021-01-07 at 20:07 -0800, Tushar Sugandhi wrote:
> Integrity critical data may belong to a single subsystem or it may
> arise from cross subsystem interaction. Currently there is no mechanism
> to group or limit the data based on certain label. Limiting and
> grouping critical data based on a label would make it flexible and
> configurable to measure.
>
> Define "label:=", a new IMA policy condition, for the IMA func
> CRITICAL_DATA to allow grouping and limiting measurement of integrity
> critical data.
>
> Limit the measurement to the labels that are specified in the IMA
> policy - CRITICAL_DATA+"label:=". If "label:=" is not provided with
> the func CRITICAL_DATA, measure all the input integrity critical data.
>
> Signed-off-by: Tushar Sugandhi <tusharsu@...ux.microsoft.com>
> Reviewed-by: Tyler Hicks <tyhicks@...ux.microsoft.com>
This is looking a lot better.
thanks,
Mimi
Powered by blists - more mailing lists