From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
James.Bottomley@HansenPartnership.com, arnd@arndb.de,
linux-integrity@vger.kernel.org
Cc: dhowells@redhat.com, sashal@kernel.org,
linux-kernel@vger.kernel.org, keyrings@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v1] IMA: fix measuring asymmetric keys Kconfig
Date: Thu, 09 Jan 2020 16:38:11 +0000 [thread overview]
Message-ID: <5411bc3d-74eb-6868-5768-bba3726a661a@linux.microsoft.com> (raw)
In-Reply-To: <1578545543.5147.32.camel@linux.ibm.com>
On 1/8/20 8:52 PM, Mimi Zohar wrote:
>
> For the time being, I've pushed out this patch with the existing patch
> description to next-integrity-testing, but the patch description
> should be rewritten clearer. For example,
>
> As a result of the asymmetric public keys subtype being defined as a
> tristate, with the existing IMA Makefile, ima_asymmetric_keys.c could
> be built as a kernel module. To prevent this from happening, this
> patch defines and uses an intermediate Kconfig boolean option named
> IMA_MEASURE_ASYMMETRIC_KEYS.
>
> Please let me know if you're ok with this wording.
>
> thanks,
>
> Mimi
>
That sounds perfect. Thanks for your help Mimi.
-lakshmi
WARNING: multiple messages have this Message-ID (diff)
From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
James.Bottomley@HansenPartnership.com, arnd@arndb.de,
linux-integrity@vger.kernel.org
Cc: dhowells@redhat.com, sashal@kernel.org,
linux-kernel@vger.kernel.org, keyrings@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v1] IMA: fix measuring asymmetric keys Kconfig
Date: Thu, 9 Jan 2020 08:38:11 -0800 [thread overview]
Message-ID: <5411bc3d-74eb-6868-5768-bba3726a661a@linux.microsoft.com> (raw)
In-Reply-To: <1578545543.5147.32.camel@linux.ibm.com>
On 1/8/20 8:52 PM, Mimi Zohar wrote:
>
> For the time being, I've pushed out this patch with the existing patch
> description to next-integrity-testing, but the patch description
> should be rewritten clearer. For example,
>
> As a result of the asymmetric public keys subtype being defined as a
> tristate, with the existing IMA Makefile, ima_asymmetric_keys.c could
> be built as a kernel module. To prevent this from happening, this
> patch defines and uses an intermediate Kconfig boolean option named
> IMA_MEASURE_ASYMMETRIC_KEYS.
>
> Please let me know if you're ok with this wording.
>
> thanks,
>
> Mimi
>
That sounds perfect. Thanks for your help Mimi.
-lakshmi
next prev parent reply other threads:[~2020-01-09 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 16:05 [PATCH v1] IMA: fix measuring asymmetric keys Kconfig Lakshmi Ramasubramanian
2020-01-08 16:05 ` Lakshmi Ramasubramanian
2020-01-09 4:52 ` Mimi Zohar
2020-01-09 4:52 ` Mimi Zohar
2020-01-09 16:38 ` Lakshmi Ramasubramanian [this message]
2020-01-09 16:38 ` Lakshmi Ramasubramanian
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=5411bc3d-74eb-6868-5768-bba3726a661a@linux.microsoft.com \
--to=nramas@linux.microsoft.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=arnd@arndb.de \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=zohar@linux.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.