linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Lakshmi Ramasubramanian <nramas@linux.microsoft.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 v11 0/6] KEYS: Measure keys when they are created or updated
Date: Thu, 12 Dec 2019 09:28:36 -0500	[thread overview]
Message-ID: <1576160916.4579.151.camel@linux.ibm.com> (raw)
In-Reply-To: <20191211164707.4698-1-nramas@linux.microsoft.com>

Hi Lakshmi,

On Wed, 2019-12-11 at 08:47 -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.

Thank you!  This patch set is now queued in the next-integrity-testing 
branch of https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-
integrity.git/.

Mimi


  parent reply	other threads:[~2019-12-12 14:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 16:47 [PATCH v11 0/6] KEYS: Measure keys when they are created or updated Lakshmi Ramasubramanian
2019-12-11 16:47 ` [PATCH v11 1/6] IMA: Check IMA policy flag Lakshmi Ramasubramanian
2019-12-11 16:47 ` [PATCH v11 2/6] IMA: Add KEY_CHECK func to measure keys Lakshmi Ramasubramanian
2019-12-11 16:47 ` [PATCH v11 3/6] IMA: Define an IMA hook " Lakshmi Ramasubramanian
2019-12-11 16:47 ` [PATCH v11 4/6] KEYS: Call the " Lakshmi Ramasubramanian
2019-12-11 16:47 ` [PATCH v11 5/6] IMA: Add support to limit measuring keys Lakshmi Ramasubramanian
2019-12-11 16:47 ` [PATCH v11 6/6] IMA: Read keyrings= option from the IMA policy Lakshmi Ramasubramanian
2019-12-12 14:28 ` Mimi Zohar [this message]
2019-12-12 16:58   ` [PATCH v11 0/6] KEYS: Measure keys when they are created or updated 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=1576160916.4579.151.camel@linux.ibm.com \
    --to=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).