[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7d9822da396a92645482e37a8c8590902323c5ef.camel@linux.ibm.com>
Date: Thu, 22 Oct 2020 16:38:58 -0400
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
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 v4 2/6] IMA: conditionally allow empty rule data
Hi Tushar,
On Wed, 2020-09-23 at 12:20 -0700, Tushar Sugandhi wrote:
> ima_match_rule_data() permits the func to pass empty func_data.
> For instance, for the following func, the func_data keyrings= is
> optional.
> measure func=KEY_CHECK keyrings=.ima
>
> But a new func in future may want to constrain the func_data to
> be non-empty. ima_match_rule_data() should support this constraint
> and it shouldn't be hard-coded in ima_match_rule_data().
>
> Update ima_match_rule_data() to conditionally allow empty func_data
> for the func that needs it.
>
> Signed-off-by: Tushar Sugandhi <tusharsu@...ux.microsoft.com>
Policy rules may constrain what is measured, but that decision should
be left to the system owner or admin.
Mimi
Powered by blists - more mailing lists