[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1573682528.4793.3.camel@linux.ibm.com>
Date: Wed, 13 Nov 2019 17:02:08 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@...ux.microsoft.com>,
dhowells@...hat.com, matthewgarrett@...gle.com, sashal@...nel.org,
jamorris@...ux.microsoft.com, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, keyrings@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 0/3] KEYS: Measure keys when they are created or
updated
On Wed, 2019-11-13 at 10:46 -0800, Lakshmi Ramasubramanian wrote:
> Keys created or updated in the system are currently not measured.
> Therefore an attestation service, for instance, would not be able to
> attest whether or not the trusted keys keyring(s), for instance, contain
> only known good (trusted) keys.
>
> IMA measures system files, command line arguments passed to kexec,
> boot aggregate, etc. It can be used to measure keys as well.
> But there is no mechanism available in the kernel for IMA to
> know when a key is created or updated.
>
> This change aims to address measuring keys created or updated
> in the system:
>
> To achieve the above the following changes have been made:
>
> - Added a new IMA hook namely, ima_post_key_create_or_update, which
> measures the key. This IMA hook is called from key_create_or_update
> function. The key measurement can be controlled through IMA policy.
>
> A new IMA policy function KEY_CHECK has been added to measure keys.
>
> # measure keys loaded onto any keyring
> measure func=KEY_CHECK
When re-posting this patch set, please include the support for
specifying the "keyrings=" policy option, as an additional patch.
Mimi
Powered by blists - more mailing lists