[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1572187644.4532.211.camel@linux.ibm.com>
Date: Sun, 27 Oct 2019 10:47:24 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>,
dhowells@...hat.com, casey@...aufler-ca.com, sashal@...nel.org,
jamorris@...ux.microsoft.com,
linux-security-module@...r.kernel.org,
linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
keyrings@...r.kernel.org
Subject: Re: [PATCH v2 1/4] KEYS: Defined an ima hook for measuring keys on
key create or update
On Fri, 2019-10-25 at 15:28 -0700, Lakshmi Ramasubramanian wrote:
> On 10/25/2019 12:40 PM, Mimi Zohar wrote:
>
> >> +void ima_post_key_create_or_update(struct key *keyring, struct key *key,
> >> + unsigned long flags, bool create)
> >> +{
> >> + const struct public_key *pk;
> >> +
> >> + if (key->type != &key_type_asymmetric)
> >> + return;
> >> +
> >> + if (!ima_initialized)
> >> + return;
> >
> > There's no reason to define a new variable to determine if IMA is
> > initialized. Use ima_policy_flag.
>
> Please correct me if I am wrong -
>
> ima_policy_flag will be set to 0 if IMA is not yet initialized
> OR
> IMA is initialized, but ima_policy_flag could be still set to 0 (say,
> due to the configured policy).
>
> In the latter case the measurement request should be a NOP immediately.
I'm not sure. The builtin keys most likely will be loaded prior to a
custom IMA policy containing "keyring" rules are defined.
Mimi
Powered by blists - more mailing lists