From: Mimi Zohar <zohar@linux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>,
James.Bottomley@HansenPartnership.com,
linux-integrity@vger.kernel.org
Cc: eric.snowberg@oracle.com, dhowells@redhat.com,
mathew.j.martineau@linux.intel.com, matthewgarrett@google.com,
sashal@kernel.org, jamorris@linux.microsoft.com,
linux-kernel@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH v6 0/3] IMA: Deferred measurement of keys
Date: Fri, 03 Jan 2020 10:08:19 -0500 [thread overview]
Message-ID: <1578064099.5874.170.camel@linux.ibm.com> (raw)
In-Reply-To: <20200103055608.22491-1-nramas@linux.microsoft.com>
Hi Lakshmi,
Instead of loosing the cover letter, Jonathan Corbet suggested
including it as the merge comment. I'd like to do that with this
cover letter.
On Thu, 2020-01-02 at 21:56 -0800, Lakshmi Ramasubramanian wrote:
> This patchset extends the previous version[1] by adding support for
> deferred processing of keys.
>
> With the patchset referenced above, the IMA subsystem supports
> measuring asymmetric keys when the key is created or updated.
The first sentence and the clause of the next sentence are
unnecessary. I would begin the cover letter with "The IMA subsystem
supports" and add the reference afterwards.
> But keys created or updated before a custom IMA policy is loaded
> are currently not measured. This includes keys added to, for instance,
> .builtin_trusted_keys which happens early in the boot process.
Let's not limit the example to just the .builtin_trusted_keys keyring.
Please update it as:
This includes keys added, for instance, to either the .ima or
.builtin_trusted_keys keyrings, which happens early in the boot
process.
>
> This change adds support for queuing keys created or updated before
> a custom IMA policy is loaded. The queued keys are processed when
> a custom policy is loaded. Keys created or updated after a custom policy
> is loaded are measured immediately (not queued).
>
> If the kernel is built with both CONFIG_IMA and
> CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE enabled then the IMA policy
> must be applied as a custom policy for the keys to be measured.
> If a custom IMA policy is not provided within 5 minutes after
> IMA is initialized, any queued keys will be freed.
As the merge message, this is too much information. I would extend
the previous paragraph and drop this one, like:
"... (not queued). In the case when a custom policy is not loaded
within 5 minutes of IMA initialization, the queued keys are freed."
> This is by design.
It's unclear what "is by design" refers to. Perhaps expand this
sentence like: "Measuring the early boot keys, by design, requires
loading a custom policy.
>
> [1] https://lore.kernel.org/linux-integrity/20191211164707.4698-1-nramas@linux.microsoft.com/
thanks,
Mimi
next prev parent reply other threads:[~2020-01-03 15:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 5:56 [PATCH v6 0/3] IMA: Deferred measurement of keys Lakshmi Ramasubramanian
2020-01-03 5:56 ` [PATCH v6 1/3] IMA: Define workqueue for early boot key measurements Lakshmi Ramasubramanian
2020-01-03 14:15 ` Mimi Zohar
2020-01-03 5:56 ` [PATCH v6 2/3] IMA: Call workqueue functions to measure queued keys Lakshmi Ramasubramanian
2020-01-03 5:56 ` [PATCH v6 3/3] IMA: Defined timer to free " Lakshmi Ramasubramanian
2020-01-03 15:08 ` Mimi Zohar [this message]
2020-01-03 15:47 ` [PATCH v6 0/3] IMA: Deferred measurement of keys Mimi Zohar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1578064099.5874.170.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dhowells@redhat.com \
--cc=eric.snowberg@oracle.com \
--cc=jamorris@linux.microsoft.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.com \
--cc=matthewgarrett@google.com \
--cc=nramas@linux.microsoft.com \
--cc=sashal@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox